/**
 * @fileoverview `brapi://variable/{observationVariableDbId}` — single
 * observation-variable record on the default connection. The single-record,
 * URI-addressable counterpart to `brapi_find_variables` (which returns a list
 * envelope). Fills the resource gap alongside `brapi://study/{id}` and
 * `brapi://germplasm/{id}`.
 *
 * Fetches the canonical `/variables/{observationVariableDbId}` payload directly
 * (trait, scale, method, ontology) and returns it verbatim — mirroring how
 * `brapi_get_germplasm` reads `/germplasm/{id}`. A 404 (or an empty record)
 * surfaces as the typed `variable_not_found` error.
 *
 * @module mcp-server/resources/definitions/brapi-variable.resource
 */
import { z } from '@cyanheads/mcp-ts-core';
import { JsonRpcErrorCode } from '@cyanheads/mcp-ts-core/errors';
export declare const brapiVariableResource: import("@cyanheads/mcp-ts-core").ResourceDefinition<z.ZodObject<{
    observationVariableDbId: z.ZodString;
}, z.core.$strip>, undefined, readonly [{
    readonly reason: "unknown_alias";
    readonly code: JsonRpcErrorCode.NotFound;
    readonly when: "No default BrAPI connection has been registered";
    readonly recovery: "Call brapi_connect (without an alias, or with alias `default`) before reading this resource.";
}, {
    readonly reason: "variable_not_found";
    readonly code: JsonRpcErrorCode.NotFound;
    readonly when: "Upstream returned no observation variable record for the requested DbId";
    readonly recovery: "Verify the observationVariableDbId on the target server, or run brapi_find_variables to discover valid IDs.";
}]>;
//# sourceMappingURL=brapi-variable.resource.d.ts.map