brapi-mcp-server

Brapi Find Germplasm

brapi_find_germplasm

Read-only

Find germplasm by name, synonym, accession number, PUI, crop, or free-text query. Matches across registered synonyms. When the upstream total exceeds loadLimit, the full result set is materialized as a dataframe — query it with brapi_dataframe_query (SQL) instead of paging row-by-row.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	Free-text query. Applied client-side as a substring match on returned rows (germplasmName, accessionNumber, defaultDisplayName, registered synonyms) — no BrAPI server reliably supports a server-side free-text filter, so combine with `crops` / `genus` / etc. to narrow the upstream pull first.
`alias`	No	Connection alias registered via brapi_connect. Omit to read the connection registered under alias `default` — i.e. a prior brapi_connect call that did not specify an alias. Calls that used a non-default alias must pass that same alias here.
`crops`	No	Filter by common crop names.
`genus`	No	Botanical genus.
`names`	No	Filter by germplasm display names.
`species`	No	Botanical species.
`synonyms`	No	Match registered synonyms.
`loadLimit`	No	Cap on rows returned inline. Omit for the deployment default. Rows beyond the cap land in a dataframe; query with brapi_dataframe_query (SQL) instead of paging row-by-row.
`collections`	No	Filter by germplasm collection names.
`extraFilters`	No	Extra BrAPI filters forwarded verbatim. Valid keys vary by endpoint; brapi_describe_filters enumerates them. Named params on this tool take precedence on conflict.
`germplasmPUIs`	No	Persistent unique identifiers.
`germplasmDbIds`	No	Filter by DbIds.
`accessionNumbers`	No	Filter by accession numbers (gene-bank catalog codes).

Output Schema

TableJSON Schema

Name	Required	Description
`alias`	No	Alias of the registered BrAPI connection the call used.
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Guidance when no rows were returned — how to broaden filters or retry.
`hasMore`	No	True when more rows exist beyond the returned set.
`results`	No	Germplasm rows returned in-context (up to loadLimit).
`warnings`	No	Advisory messages (filter overrides, partial data, capability gaps).
`dataframe`	No	Dataframe handle when the full result set was materialized as a dataframe. Query it with brapi_dataframe_query (SQL).
`totalCount`	No	Total rows reported by the server.
`distributions`	No	Value frequency per field across the full result set.
`returnedCount`	No	Length of results[].
`appliedFilters`	No	The final filter map sent to the server (named + extraFilters).
`refinementHint`	No	Suggested next-step query refinement when the result set is large.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: it discloses that large result sets are materialized as a dataframe and that matching works across registered synonyms, which helps agents anticipate how queries behave at scale. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, with the core purpose front-loaded and the large-result behavior attached as an important follow-up. Every word earns its place; there is no filler or repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 13 optional parameters, a full output schema, and read-only/open-world annotations. The description covers the essential workflow, including the critical performance caveat about loadLimit and dataframe materialization, so an agent has what it needs to invoke the tool and interpret large results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 13 parameters in detail. The description's brief enumeration (name, synonym, accession number, PUI, crop, free-text) adds no meaning beyond that, but given full schema coverage, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Find germplasm' — and enumerates the supported search facets: name, synonym, accession number, PUI, crop, and free-text query. It also adds a distinctive behavior, matching across registered synonyms, which clearly separates this search tool from direct retrieval tools like brapi_get_germplasm.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit routing instruction: when the upstream total exceeds loadLimit, use brapi_dataframe_query instead of paging row-by-row. This gives clear context for a key decision point. It does not enumerate exclusions against every sibling (e.g., brapi_get_germplasm for direct ID lookups), but the main alternative is named with a trigger condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All brapi-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.