Skip to main content
Glama

wheat_knockout_screen

Read-onlyIdempotent

Which genes have EMS alleles in every homoeologue, i.e. can be knocked out across A, B and D by crossing Cadenza/Kronos lines. For each gene (genes: up to 300 symbols or IWGSC IDs, or region: RefSeq v1.0 interval up to 10 Mb, e.g. a QTL) the A/B/D copies come from Ensembl Compara, and each copy gets its lines with a consequence 'truncating' (default; stop, splice donor/acceptor, start/stop lost) or 'missense' etc. Status 'all_copies', 'partial' or 'none'; complete_only keeps 'all_copies'. Kronos lines cover only A and B copies; D copies need Cadenza. Lines hitting two copies at once are flagged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wheat_knockout_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
genesNo
limitNo
regionNo
consequenceNotruncating
complete_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's value is the added context it does supply: A/B/D copies come from Ensembl Compara, Kronos covers only A and B while D requires Cadenza, lines hitting two copies at once are flagged, and results carry a status of all_copies/partial/none. The provenance and coverage caveats are exactly the kind of behavior an agent cannot get from structured fields. It stops short of describing the shape of the per-gene/per-copy result.

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 and every clause carries information — no filler sentences. The trade-off is dense run-on phrasing with nested parentheticals ("For each gene (genes: ... or region: ...) the A/B/D copies ...") that takes a second pass to parse, but no content is redundant.

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, a five-parameter schema at 0% coverage, and non-trivial cross-referencing logic, the description still supplies provenance, coverage limits, consequence classes, status vocabulary and the two-copy flag. The remaining gaps are the undocumented limit parameter and the absence of any description of the returned per-gene result structure.

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 must carry parameter meaning and largely does: genes accepts up to 300 symbols or IWGSC IDs, region is a RefSeq v1.0 interval up to 10 Mb (e.g. a QTL), consequence defaults to truncating with enumerated classes given inline, and complete_only is explained via its all_copies filter. The limit parameter (default 100) is never mentioned, and it is not stated whether genes and region are mutually exclusive.

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 states a precise, non-generic operation: finding genes with EMS alleles in every homoeologue so they can be knocked out across A, B and D by crossing Cadenza/Kronos. The verb+resource are unambiguous and the framing question makes the tool's role obvious. It does not explicitly contrast itself with the nearest siblings (wheat_mutants / wheat_mutant_line), which keeps it off a 5.

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 implied by the scenario (QTL region or gene list, complete knockout only) and the defaults are stated, but there is no explicit when-to-use/when-not or a named alternative such as wheat_mutants for a single line lookup. The reader must infer routing from domain knowledge.

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