Skip to main content
Glama

find_germplasm

Read-onlyIdempotent

Find pulse and legume genebank accessions by accession number or name (e.g. 'ICC 4958' for chickpea at ICRISAT): chickpea, lentil, pea, faba bean, lupin, grass pea, Phaseolus, Vigna, pigeonpea, soybean, peanut and Medicago accessions from GBIF, with the holding genebank (FAO WIEWS code, e.g. IND002 = ICRISAT, SYR002/LBN002 = ICARDA) and accession number; mostly Svalbard safety duplicates. Passport data are minimal (no traits). Also INRAE GnpIS pea and faba bean collections via FAIDARE, with taxon, holding institute, country of origin, status, pedigree and panels.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare the read-only, idempotent, open-world, non-destructive profile, so the safety picture is covered. The description does add genuine behavioral context beyond that: provenance (GBIF vs FAIDARE), the fact that records are 'mostly Svalbard safety duplicates', and that passport data are minimal. It stops short of describing matching semantics (exact vs partial accession match) or result ordering, which matter for an open-world search tool.

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

Conciseness3/5

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

The verb, identifier example, and scope are front-loaded correctly, and the second sentence cleanly separates the INRAE/FAIDARE source. However, the twelve-taxon enumeration and the WIEWS-code explanation consume substantial space for information that is partly redundant with the source description, making it a dense run-on rather than a tight statement.

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?

With no output schema, the description correctly compensates by enumerating returned fields (holding genebank WIEWS code, accession number, taxon, country of origin, status, pedigree, panels). Gaps remain for a two-parameter open-world search: no statement on result volume, truncation, or matching behavior, which an agent needs to decide whether one call suffices.

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

Parameters2/5

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

Schema coverage is 0%, so the description must carry both parameters. It does clarify the required 'name' parameter's accepted forms (accession number or free name, with 'ICC 4958' as a format example), but the 'limit' parameter with its default of 10 is never mentioned and no guidance is given on paging or what happens when more accessions match.

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 verb (Find) and a concrete resource (pulse and legume genebank accessions), then names the identifier formats ('accession number or name', with the 'ICC 4958' example) and the exact taxa and upstream sources covered. No sibling tool in the list deals with germplasm accessions, so the scope is unambiguous 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?

The description establishes clear usage context: use it for genebank accession lookup by accession code or name, and it warns the returned data are passport-level only. The parenthetical 'no traits' implicitly routes trait-seeking agents elsewhere, but no alternative tool is named explicitly and there is no statement about what to do when a lookup returns nothing.

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