Skip to main content
Glama

brapi_germplasm_studies

Read-onlyIdempotent

Phenotyping studies (field and glasshouse trials) with trait data for a Brassica line, live from the BrAPI nodes (currently the INRAE Brassica trials in GnpIS (rapeseed and cabbage collections), 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.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is data provenance and matching behavior: the data is live from BrAPI nodes and currently limited to INRAE Brassica trials. The exact-match-with-case-fallback semantics is genuinely useful behavior disclosure beyond the annotations.

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 purpose, the parameter semantics, the return contents, and the sibling routing are all front-loaded and each sentence carries information. The nested parenthetical about GnpIS/FAIDARE is dense but conveys real data-scope information rather than filler.

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 correctly enumerates what is returned: germplasm records with source, holding institute, and accession, plus each study's name, trial/network, season, location, observation count, variables, and link. The only gap is the undocumented limit/pagination parameter.

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 0%, but the description explains the critical 'germplasm' parameter well: exact match with upper/title case fallback, with a concrete example. However, the 'limit' parameter (default 200) is never mentioned, so it does not fully compensate for zero schema coverage.

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?

States a specific resource (phenotyping studies with trait data for a Brassica line) and a specific scope, plus where the data comes from (INRAE Brassica trials in GnpIS via FAIDARE). It clearly distinguishes itself from the sibling brapi_observations, which it routes to for trait values.

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?

Explicitly names the alternative for trait values ('Use brapi_observations for the trait values'), which is a real when-to-use-which rule. It does not address when to use this instead of find_germplasm or the other germplasm-adjacent siblings, so it falls short of full exclusion guidance.

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