Skip to main content
Glama

brapi_observations

Read-onlyIdempotent

Trait observations for a wheat line from the BrAPI nodes (currently the INRAE wheat trial network and Whealbi trials in GnpIS, served through FAIDARE), summarised per study and variable: n, mean, min, max (numeric values) or the distinct values, season and location. germplasm: line name (as in brapi_germplasm_studies). trait filters variables by name or ontology ID part (e.g. 'rdt', 'CO_321:1000074', 'yield'; INRAE short names are glossed: rdt = grain yield, prot = grain protein, pmg = thousand-grain weight, ht = plant height, rj/rb = yellow/brown rust). study filters by study name part (e.g. 'Le_Moulon', '2015'). Compare values within a study.

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_observations"
  }
}

Input Schema

NameRequiredDescriptionDefault
studyNo
traitNo
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, openWorld), and the description adds real behavioral context beyond them: the exact summary shape returned (n, mean, min, max for numeric; distinct values otherwise, plus season and location) and the limited, evolving source coverage signalled by 'currently'. It stops short of describing empty-result behavior, coverage limits per study, or how many studies come back by default.

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?

Front-loaded with the core purpose and return shape, and every element (glosses, source list, examples) is functionally useful rather than filler. Structure suffers slightly from the long parenthetical gloss list embedded mid-sentence and a run-on paragraph format, but no sentence is truly wasted.

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?

For a three-parameter read-only tool with no output schema and adequate annotations, the description covers inputs, return shape, and data provenance well enough to call it correctly. What is missing is edge-case behavior (unknown germplasm, no observations found) and how many studies are returned when no study filter is supplied.

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?

With 0% schema description coverage the description must carry all parameter meaning, and it largely does: germplasm is the line name as used in brapi_germplasm_studies, trait accepts a name or ontology-ID part with worked examples and INRAE short-name glosses, and study matches on a study name part. The one gap is that germplasm matching is left ambiguous (exact vs. substring) while the other two are explicitly 'part' matches.

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?

Names a specific verb+resource (trait observations for a wheat line from BrAPI nodes) and states the aggregation grain (per study and variable). It also scopes the data sources (INRAE wheat trial network, Whealbi trials in GnpIS via FAIDARE) and explicitly ties germplasm naming to the sibling brapi_germplasm_studies, so it is distinguishable from generic phenotype siblings.

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

Usage Guidelines3/5

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

Provides implied usage guidance with the closing 'Compare values within a study' and shows concrete filter examples ('Le_Moulon', '2015', 'rdt'), which tells an agent how to narrow queries. However, it never states when to prefer this over alternatives such as genebank_phenotypes, snp_phenotypes or trait_hits, nor any prerequisite or exclusion.

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