Skip to main content
Glama

wheat_mutant_line

Read-onlyIdempotent

Every mutation Ensembl lists for one EMS line (Cadenza or Kronos exome-capture TILLING; Krasileva et al. 2017), e.g. 'Cadenza1166' or 'Kronos2235': counts by consequence, the genes with truncating mutations, and the mutations (gene, consequence, amino-acid change, RefSeq v1.0 position), most severe first. consequence filters as in wheat_mutants ('truncating', 'missense', ...); chromosome e.g. '6D'. Use it to judge a line's background load and to check for off-target hits near a gene of interest before crossing.

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": {
      "line": "<line>"
    },
    "name": "wheat_mutant_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYes
limitNo
chromosomeNo
consequenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower; the description adds real context beyond them by naming the data source (Ensembl, Krasileva et al. 2017), the population type (exome-capture TILLING), the result ordering (most severe first), and the reference coordinate system (RefSeq v1.0). It omits anything about result volume or the effect of the default limit.

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 the core statement and its payload, then filters, then usage — a sensible order with no filler sentences. The long appositive parentheticals (citation, field list) make it denser than necessary but every clause still carries information.

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?

There is no output schema, and the description largely compensates by enumerating returned fields, but gaps remain: behavior of `limit`/pagination and whether counts are returned alongside the full mutation list are unstated. For a four-parameter data-retrieval tool this is adequate but not fully self-contained.

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?

With schema description coverage at 0%, the description must carry parameter meaning, and it does for three of four: `line` is illustrated with real IDs, `consequence` is explained with accepted values ('truncating', 'missense') and cross-referenced to wheat_mutants, and `chromosome` gets a format example ('6D'). The `limit` parameter (default 200) is left entirely unexplained.

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+resource: all mutations Ensembl lists for one EMS TILLING line ('Cadenza1166', 'Kronos2235'), with an explicit description of the payload (per-consequence counts, genes with truncating mutations, mutation records sorted most severe first). It is clearly distinct from the sibling wheat_mutants, which it references only for filter semantics.

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 concrete use cases: judging a line's background mutation load and checking off-target hits near a gene of interest before a cross. It does not state when this is a poor choice versus a broader variant search (e.g. wheat_variants_in_region), but the intended workflow context is clear.

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