Skip to main content
Glama

brapi_germplasm_studies

Read-onlyIdempotent

Phenotyping studies (field and glasshouse trials) with trait data for a wheat line, live from the BrAPI nodes (currently the INRAE wheat trial network and Whealbi trials in GnpIS, served through FAIDARE). germplasm: a cultivar or line name (matched exactly; upper/title case are tried too, e.g. 'Soissons' -> 'SOISSONS'). Returns the matching germplasm records (source, holding institute, accession) and each study's name, trial/network, season, location, number of observations, variables measured and link. Use brapi_observations for the trait values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "germplasm": "<germplasm>"
    },
    "name": "brapi_germplasm_studies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
germplasmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower; the description nonetheless adds real context beyond them: the data is live, sourced only from specific BrAPI nodes (INRAE wheat trial network, Whealbi trials in GnpIS via FAIDARE), and it spells out the return payload shape. It does not mention rate limits or what an empty result looks like, but coverage is well above the annotation baseline.

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

Conciseness4/5

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

The core purpose and the sibling hand-off are front-loaded, and the return-value enumeration earns its space because there is no output schema. Some minor waste and an awkward line break inside the germplasm explanation slightly hurt readability.

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

Completeness4/5

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

With no output schema, the description compensates by enumerating the returned germplasm and study fields (source, institute, accession, trial/network, season, location, observation count, variables, link). Only pagination/limit behavior and the no-match case are left unaddressed for a two-parameter read tool.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the parameter burden, and it does for the required 'germplasm' param: exact-match semantics, automatic upper/title-case retries, and a concrete example ('Soissons' -> 'SOISSONS'). The optional 'limit' param is never mentioned, which keeps it from a 5.

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+resource ('Phenotyping studies (field and glasshouse trials) with trait data for a wheat line') and immediately distinguishes itself from brapi_observations, which supplies the trait values. An agent can tell exactly what this returns without opening the schema.

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?

It gives an explicit routing rule to the sibling tool ('Use brapi_observations for the trait values'), which is the main selection risk here. It does not state when this tool should not be used (e.g. non-wheat germplasm or lines absent from the INRAE/Whealbi nodes), but the live-source scoping implies those limits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources