Skip to main content
Glama

brapi_observations

Read-onlyIdempotent

Trait observations for a Brassica line from the BrAPI nodes (currently the INRAE Brassica trials in GnpIS (rapeseed and cabbage collections), 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.5/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 bar is lower; the description still adds real behavioral context: results are summarised aggregates (n, mean, min, max for numeric traits, distinct values otherwise) plus season and location, and the closing caveat signals that cross-study comparison is not valid. It omits coverage/limits details such as what happens when a line has no observations in a study.

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?

Nearly every clause earns its place: the trait glossary and filter examples are directly actionable, and the purpose is front-loaded. The structure is a single dense run-on with an awkward mid-text line break and no separation between purpose, parameter notes, and usage caveat, which costs a little scannability.

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?

With no output schema, the description compensates by explaining exactly what comes back (n, mean, min, max or distinct values, season, location). All three parameters, the required germplasm workflow, and the within-study comparison caveat are covered, leaving nothing an agent would need before calling the tool.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so for all three parameters: germplasm is a line name using brapi_germplasm_studies conventions, trait accepts a name or ontology ID fragment with examples ('rdt', 'CO_321:1000074', 'yield') and a glossary of INRAE short names, and study is a partial study-name match with examples. The substring-matching semantics ('name part') are information the bare schema does not provide.

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 opening states a specific verb and resource (trait observations for a Brassica line), names the data provenance (INRAE Brassica trials in GnpIS via FAIDARE), and describes the aggregation unit (per study and variable). It also explicitly ties the germplasm parameter format back to brapi_germplasm_studies, so an agent can distinguish it from that sibling.

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 gives clear context for use, including the workflow pointer that the germplasm value must match the naming used in brapi_germplasm_studies, and closes with the practical instruction 'Compare values within a study.' It does not, however, tell the agent when to prefer this over other phenotype-like siblings (e.g. snp_phenotypes, trait_hits) or state any exclusion conditions.

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