Skip to main content
Glama

watkins_lof_alleles

Read-onlyIdempotent

Watkins landraces and modern cultivars carrying a predicted loss-of-function allele of a gene (WatSeq, 1,051 accessions): each stop-gained, start/stop-lost or splice-site SNP with its protein change, the number of homozygous and heterozygous carriers, and the carriers (accession, ancestral group, country) for ordering from the JIC Germplasm Resources Unit. gene: symbol or any IWGSC ID; homoeologues are listed for checking redundancy.

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

Input Schema

NameRequiredDescriptionDefault
geneYes
carriersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds real context beyond them: the underlying dataset and size, exactly which columns come back (protein change, homozygous vs heterozygous carrier counts, accession/ancestral group/country), the downstream purpose (ordering from JIC GRU), and the redundancy caveat about homoeologues. It does not disclose any result-size or pagination behavior, even though the 'carriers' parameter default of 100 hints at a cap.

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?

One dense paragraph that front-loads what the tool returns and then covers input format and the homoeologue caveat; nearly every clause carries information. The nested parentheticals make it slightly harder to scan, but there is no filler.

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 does the necessary work of enumerating the returned fields and the dataset scope, which is the main completeness burden here. The remaining gap is the undocumented 'carriers' parameter and the absence of any result-limit behavior, which matters for a query that could return many carriers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 parameter meaning. It does this well for 'gene' (symbol or any IWGSC ID), which is meaningful added value over the bare string schema, but the second parameter 'carriers' (integer, default 100) is never mentioned, so its meaning — presumably how many carriers to return — is left entirely undocumented.

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 states a specific resource and scope: LoF alleles of a gene across Watkins landraces and modern cultivars (WatSeq, 1,051 accessions), including the variant types (stop-gained, start/stop-lost, splice-site) and the carrier detail returned. It doesn't explicitly name a sibling to distinguish from, e.g. watkins_accession_lof or watkins_gene_accessions, but the gene-centric allele view is clear enough that an agent can identify the right tool.

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 rather than stated: query by gene symbol/IWGSC ID when you want LoF carriers, and note that homoeologues are listed so redundancy can be checked. There is no explicit when-not guidance or reference to the per-accession sibling (watkins_accession_lof), leaving the agent to infer which of the several Watkins tools to pick.

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