Skip to main content
Glama

wheat_gene_catalogue

Read-onlyIdempotent

Catalogue of Gene Symbols for Wheat (McIntosh et al., GrainGenes; 2024 edition): the official register of designated wheat genes and alleles. query: a gene or allele symbol ('Lr34', 'Rht-B1b'), locus ('Rht-B1' lists all its alleles), old synonym ('Rht1', 'Ppd1', 'NAM-B1'), trait words matching a catalogue section ('stem rust', 'height', 'vernalization', 'glutenin') or any text (a cultivar, marker or stock name). chromosome filters by arm or chromosome ('2D', '7DS'). Each entry gives its section, synonyms, chromosome, the catalogue text (stocks i:/v:, markers ma:, cloning c:) and, with full, the cited references resolved. Use resolve_gene for the IWGSC gene ID of cloned genes.

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

Input Schema

NameRequiredDescriptionDefault
fullNo
limitNo
queryYes
chromosomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds substantive behavior the annotations cannot: each entry returns its section, synonyms, chromosome, catalogue text annotated with stock (i:/v:), marker (ma:) and cloning (c:) codes, and references only when full is set. No pagination or rate-limit behavior is described.

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 resource identity is front-loaded before the parameter guidance, and the parenthetical examples do real work by disambiguating accepted inputs. It is dense but free of filler; the long parenthetical enumerations of query forms and entry codes make it heavier to parse than necessary.

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 appropriately explains what an entry contains and when references are resolved. For a read-only search tool with four simple parameters this is nearly sufficient; only result-volume/limit behavior is unaddressed.

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?

Schema description coverage is 0%, so the description carries the full burden, and it does: query is elaborated with five concrete accepted input forms including example strings, chromosome is defined as arm or chromosome ('2D', '7DS'), and full is explained as gating reference resolution. Only limit is left undefined beyond its schema default of 20.

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 description names the specific resource and scope: the official register of designated wheat genes and alleles (McIntosh et al., GrainGenes 2024). It distinguishes itself from resolve_gene by delegating IWGSC gene ID lookups, so an agent can separate the two without opening either 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?

It spells out exactly what forms the query accepts (symbol, locus, old synonym, trait/section word, arbitrary text such as cultivar or marker) and gives the explicit alternative for cloned-gene IDs: 'Use resolve_gene for the IWGSC gene ID of cloned genes.' It does not state when to prefer a per-gene viewer such as wheat_gene_view, but the positive routing guidance is strong.

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