Skip to main content
Glama

snp_lines

Read-onlyIdempotent

Find SNP-genotyped lines in CropSNPdb by name or AGG accession (e.g. 'Cadenza', 'AGG 38862', 'CAIGE ZWB17' or a CAIGE GID '7396745'). Returns line name, accession(s), country, pedigree, status, breeding organisation and donor. dataset: 'wheat40k' (default) or 'wheat90k'.

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": {
      "query": "<query>"
    },
    "name": "snp_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
datasetNowheat40k

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds real value beyond them by listing the returned fields and explaining the dataset switch with its default. It omits match semantics (exact vs partial/substring) and any behavior around the limit default, which would have pushed this higher.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the searchable identifiers and examples come first, the return payload second, and the dataset option last. Every clause carries information an agent needs.

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, the description correctly enumerates return fields, and it documents the dataset enum that the schema leaves bare. It is nearly complete for a three-parameter read tool; only the `limit` parameter and result-matching behavior are left unaddressed.

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 the load, and it does for two of three parameters: `query` gets four concrete input formats and `dataset` gets both allowed values plus the default. The `limit` parameter is never mentioned, leaving one parameter undocumented in both schema and description.

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 names a specific verb and resource ('Find SNP-genotyped lines in CropSNPdb') and scopes it to lookup by name or accession. It implicitly separates itself from genotype/marker/haplotype siblings by being a line-search tool, but never names an alternative such as ozwheat_lines or find_germplasm.

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 through concrete query examples ('Cadenza', 'AGG 38862', 'CAIGE ZWB17', CAIGE GID '7396745'), which tells the agent what inputs are valid. There is no explicit when-to-use versus when-to-use-another-tool guidance, and no mention of the neighbouring line-search tools.

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