Skip to main content
Glama

wheat_homologues

Read-onlyIdempotent

Homoeologues (the A/B/D copies), and orthologues in other grasses and Arabidopsis, of a bread wheat gene from Ensembl Plants Compara gene trees. gene: symbol or any IWGSC ID (converted to RefSeq v1.1). By default orthologues are listed for durum and wild emmer, T. urartu, Ae. tauschii, rye, barley, oat, Brachypodium, rice, maize, sorghum and Arabidopsis; target_species takes Ensembl names instead (e.g. ['triticum_aestivum_mace', 'hordeum_vulgare_goldenpromise'] for pan-genome cultivars). include_paralogues adds within-wheat paralogues (same-genome duplicates). Relationships: homoeolog_one2one, ortholog_one2one/one2many/many2many.

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

Input Schema

NameRequiredDescriptionDefault
geneYes
target_speciesNo
include_paraloguesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds real behavioral payload beyond them: the underlying data source, that gene IDs are silently converted to RefSeq v1.1, the exact default species panel applied when target_species is null, and the relationship vocabulary returned (homoeolog_one2one, ortholog_one2one/one2many/many2many). That tells the agent both what will come back and what happens when optional parameters are omitted.

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 what is returned, then parameters, then the relationship vocabulary; no filler sentences. It is packed into a dense run-on with embedded line breaks and a long species enumeration, which costs some scannability even though each clause carries information.

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?

Three parameters, no output schema, and the description covers input formats, defaults, option semantics, data provenance, and the shape of returned relationships. An agent has enough to call this correctly without further lookup.

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. gene accepts a symbol or any IWGSC ID with an implicit conversion step, target_species must use Ensembl names 'instead' of the defaults with a worked example, and include_paralogues is defined as within-wheat same-genome duplicates — a distinction that is genuinely non-obvious from the parameter name.

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?

States a specific resource set: homoeologues (A/B/D copies) plus orthologues in other grasses and Arabidopsis, sourced from Ensembl Plants Compara gene trees for a bread wheat gene. That is far more precise than 'homologues', and the Compara-tree framing implicitly separates it from the expression-oriented sibling. It stops short of naming any sibling tool or an explicit exclusion, which keeps it out of 5 territory.

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?

Gives the agent concrete context for each branch of use: default orthologue listing across a named species panel, target_species when Ensembl naming or pan-genome cultivars are wanted, and include_paralogues when within-wheat duplicates are needed. No explicit when-not-to-use or pointer to an alternative tool, so it is clear-but-unrouted rather than complete.

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