Skip to main content
Glama

find_germplasm

Read-onlyIdempotent

Find wheat accessions/cultivars/lines by name or accession ID across five indexed sources: CropSNPdb (SNP-genotyped lines, incl. all Australian Grains Genebank wheat and CAIGE breeding lines), the Watkins Wheat Pangenome (sequenced landraces), OzWheat (CSIRO GWAS panel lines), FAIDARE (INRAE GnpIS collections, e.g. the FRA040 Clermont-Ferrand wheat collection, and EVA European genebank evaluation sets) and genebank accessions of Triticum and Aegilops from GBIF (holding genebank as FAO WIEWS code, e.g. MEX002 = CIMMYT, accession number; mostly Svalbard safety duplicates).

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": {
      "name": "<name>"
    },
    "name": "find_germplasm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds domain context (what each source contains, the WIEWS-code holding convention) but says nothing about match semantics (exact vs fuzzy, cross-source deduplication) or ordering of results, which is what an agent actually needs to interpret a call.

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?

A single front-loaded sentence where the verb and resource come first, followed by the source inventory. It is dense and the parenthetical detail about FAO WIEWS codes and Svalbard duplicates could be trimmed, but nothing is redundant with structured fields.

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

Completeness3/5

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

For a two-parameter read-only search with no output schema, the description covers sources and the name/ID duality but leaves the result shape undefined — an agent cannot tell what fields come back per source or how many results per source the limit applies to.

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%, so the description must carry the parameter meaning. It does clarify that 'name' accepts either a cultivar/line name or an accession ID, which is genuine added value, but the 'limit' parameter is never mentioned and no format example for accession IDs is given.

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

Purpose4/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 wheat accessions/cultivars/lines by name or accession ID') and enumerates exactly which datasets are searched. That scope makes it distinguishable from single-source siblings such as ozwheat_lines or watkins_accession, though it never explicitly contrasts itself with them.

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?

Usage is only implied: the tool is for locating germplasm by name or accession ID, and the source list signals when a given line would be found here versus in a source-specific tool. There is no explicit when-to-use/when-not statement and no guidance on choosing between this and the per-source lookup tools.

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