Skip to main content
Glama

wheat_variants_in_region

Read-onlyIdempotent

EMS mutations and exome-capture variants in a bread wheat interval on IWGSC RefSeq v1.0, including intergenic ones (promoters, unannotated regions, off-target capture). region: 'chr:start-end', e.g. '3A:100000000-100500000' (max 5 Mb). source 'ems', 'diversity' or 'all' (default); consequence as in wheat_mutants, plus 'intergenic'. Genic variants name the gene (RefSeq v1.1); use genes_in_region for the genes near intergenic ones.

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": {
      "region": "<region>"
    },
    "name": "wheat_variants_in_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
regionYes
sourceNoall
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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: a 5 Mb maximum interval, the reference assembly used for coordinates (v1.0) versus gene naming (v1.1), and the fact that off-target capture and unannotated regions are included — all of which affect result interpretation.

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?

Three dense sentences, front-loaded with what the tool returns before moving to parameter syntax and the sibling pointer. Nearly every clause earns its place, though the first sentence is heavy with parenthetical detail that could be tightened.

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?

No output schema exists, so the description should signal the shape of results; it does so only partially by noting that genic variants name the gene (RefSeq v1.1) and that intergenic records exist. The unexplained limit parameter and absent guidance on result volume/ordering leave a moderate gap for a query that can return hundreds of records.

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 0% schema description coverage, the description must carry the parameter burden, and it does for three of four: region syntax with a concrete example ('3A:100000000-100500000') and the 5 Mb cap, the source values ('ems', 'diversity', 'all' default), and the consequence vocabulary plus 'intergenic'. The 'limit' parameter (default 200) is never mentioned, leaving pagination/truncation behavior undocumented.

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-like operation and resource: EMS mutations and exome-capture variants within a named wheat interval on IWGSC RefSeq v1.0. It explicitly carves out its distinguishing scope ('including intergenic ones (promoters, unannotated regions, off-target capture)'), which separates it from the genic-only sibling tools without needing to open a 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?

Gives a clear routing rule: use genes_in_region for the genes near intergenic hits, and references wheat_mutants as the baseline for consequence values, implying a shared vocabulary. It stops short of stating when to prefer this over wheat_mutants outright (e.g. region sweep vs. line lookup), so an agent must infer that boundary.

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