Skip to main content
Glama

wheat_gene_view

Read-onlyIdempotent

Interactive gene view for one bread wheat gene: a relationship map of its A/B/D homoeologues, orthologues (durum, Ae. tauschii, barley, rice, maize, Arabidopsis and others), EMS knockout lines per copy, Watkins haplotypes, expression responses and recent papers, with tabs for mutations along the gene and the haplotype map. Clients that support MCP Apps show it in the chat; the result also lists the nodes and the askWheat gene page link (page) to share. gene: symbol or any IWGSC ID.

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_gene_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: that MCP-Apps-capable clients render it in chat, and that the result also returns the node list plus an askWheat page link suitable for sharing — telling the agent the call has a side channel (a shareable URL) beyond the data itself.

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?

Purpose is front-loaded in the first clause, and the second sentence covers rendering and the returned link. The long parenthetical species/feature list is dense but each item conveys what the view surfaces; a mild trimming opportunity exists but nothing is truly wasted.

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 one required parameter and no output schema, the description gives an adequate behavioral picture: it names the return payload (nodes plus page link) and how clients display it. Minor gaps remain around unresolved gene identifiers or behavior in non-MCP-Apps clients, but nothing blocks a correct invocation.

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 burden, and it does: 'gene: symbol or any IWGSC ID' tells the agent the two accepted identifier forms, which the bare string schema does not. It stops short of giving an example value or stating what happens with an ambiguous symbol.

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 concrete resource ('gene view for one bread wheat gene') and enumerates what the view contains: A/B/D homoeologues, orthologues across named species, EMS knockouts, Watkins haplotypes, expression and papers. That breadth also implicitly separates it from the narrower siblings like wheat_homologues or wheat_gene_haplotypes, which cover only one slice of the same data.

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?

The 'interactive ... view for one gene' framing plus the node list implies a broad overview use case, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative for an agent that only needs, say, orthologues or knockout lines. Guidance is inferable rather than stated.

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