Skip to main content
Glama

watkins_accession

Read-onlyIdempotent

One Watkins accession (e.g. WATDE0063, or a synonym): origin, ancestral group, coordinates, Seedstor link, number of genes present, presence/absence of the listed genes (symbols or any IWGSC IDs accepted), all its phenotype records (trial, trait, value, units) and any RIL populations it is a parent of.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
genesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the safety profile is settled. The description adds real value by disclosing the response contents (identity, provenance, coordinates, external link, gene counts, phenotype records, and population parentage) and by noting that synonyms and any IWGSC ID forms are accepted. It stops short of stating behavior when the accession name is unknown or how large the phenotype payload can get, which keeps it below a 5.

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?

A single sentence, front-loaded with the identity and example, followed by the return payload as a compact list. No filler, no restatement of the tool name, and every clause conveys scoping information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must describe what comes back, and it enumerates the return fields thoroughly enough for an agent to decide whether it needs this call. For a two-parameter read-only lookup, the remaining gap (missing-record behavior) is minor.

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 coverage is 0% and neither parameter carries a description, so the description has to carry the load — and it does. It gives a concrete format example for 'name' (WATDE0063, or a synonym) and explicitly defines the accepted vocabulary for 'genes' (symbols or any IWGSC IDs), which is information an agent cannot get from the bare schema.

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-resource pair ('One Watkins accession') and enumerates exactly what a returned record contains: origin, ancestral group, coordinates, Seedstor link, gene counts, gene presence/absence, phenotype records, and RIL parentage. An agent knows this is the single-accession detail lookup, distinct from list/aggregate siblings, though no sibling is named explicitly.

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 only implied: fetching 'one' accession suggests the per-record lookup path, and the example 'WATDE0063, or a synonym' hints at accepted identifier forms. There is no explicit statement of when to prefer this over watkins_phenotypes, watkins_gene_presence, or a find-style sibling, and no exclusion or precondition guidance.

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