Skip to main content
Glama

snp_lines

Read-onlyIdempotent

Find SNP-genotyped lines in CropSNPdb by name or AGG accession (e.g. 'Westar', 'Darmor'). Returns line name, accession(s), country, pedigree, status, breeding organisation and donor. dataset: 'Brassica napus Darmor v81' (default, 459 lines), 'Brassica napus Darmor v41', 'Brassica rapa v3', 'Brassica oleracea v2.1', 'Brassica juncea v1.5' (all Brassica 60K array); 'bnapus_pangenome' (53 B. napus pangenome accessions, 1.36 M WGS SNPs, Darmor v8.1 chromosomes A01-C09; keep regions small for genotypes).

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
datasetNoBrassica napus Darmor v81

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 declare readOnly, idempotent, non-destructive, open-world lookup, so safety is covered. The description goes further by enumerating the curated metadata returned (line name, accession(s), country, pedigree, status, breeding organisation, donor) and by characterizing each dataset's contents, which is real added context given no output schema.

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, front-loaded with the purpose and search keys, followed by the return fields and the dataset catalog. The long dataset enumeration earns its space because the parameter enum is otherwise undocumented in the schema.

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, describing the returned fields and the dataset variants covers nearly everything needed to call this correctly. The only gap is the unspecified `limit` behavior (whether it truncates results and in what order), which matters for interpreting partial results.

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. It explains the required `query` (name or AGG accession with examples) and enumerates the valid `dataset` values including the default, which the schema leaves as a bare string. The `limit` parameter (default 50) goes unmentioned in both places.

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?

States a specific verb and resource: 'Find SNP-genotyped lines in CropSNPdb by name or AGG accession', with concrete example queries ('Westar', 'Darmor'). The role is clear, but it never contrasts itself with close siblings such as snp_genotypes or snp_compare_lines, so an agent must infer the boundary from names alone.

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 'by name or AGG accession' phrasing and by the enumerated dataset choices, which include size hints (459 lines, 53 pangenome accessions). There is no explicit when-to-use/when-not guidance and no named alternative for retrieving genotypes rather than line metadata; the note 'keep regions small for genotypes' is really advice for a different tool and slightly blurs the scope.

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