Skip to main content
Glama

watkins_accession_lof

Read-onlyIdempotent

Genes with a predicted loss-of-function allele (stop gained, start/stop lost, splice site) in one Watkins landrace or modern cultivar (WatSeq). accession: Watkins store code or WatSeq sample name (e.g. 'Watkins 1190027', 'WATDE0027', 'Paragon'). genes optionally restricts to a gene list (symbols or IWGSC IDs). Rare alleles (carried by few accessions) are listed first.

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

Input Schema

NameRequiredDescriptionDefault
genesNo
limitNo
accessionYes
homozygous_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real behavior beyond them: the variant classes counted as LOF and the result ordering that surfaces rare alleles first. It omits consequential behavior such as the default limit of 500 and what happens on truncation, and never explains that results are filtered to homozygous calls by default.

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?

The core scope is front-loaded in the first clause and every sentence carries information; the parameter notes are compact and example-driven. The prose is somewhat run-on, mixing purpose, parameter formats, and ordering in one paragraph without visual separation.

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?

With no output schema, the description should convey what a result row looks like, but it does not. It also leaves a behaviorally significant default (homozygous_only) undocumented, though the accession-format examples and ordering note cover the most error-prone parts of the call.

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

Parameters2/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 full burden. It does well on two parameters, giving accepted accession formats with concrete examples and clarifying that genes accepts symbols or IWGSC IDs, but it says nothing about limit or homozygous_only, the latter defaulting to true and materially changing which variants are returned.

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 (genes carrying a predicted loss-of-function allele) with a precise scope (one Watkins landrace or modern cultivar from WatSeq) and even enumerates which variant classes count. It does not explicitly contrast itself with the sibling watkins_lof_alleles, so the inverse relationship must be inferred from the name 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 rather than stated: the singular-accession framing and the optional gene-list restriction make the intended call pattern reasonably clear, and the note that rare alleles come first hints at the intended analysis. However, there is no explicit when-to-use statement, no mention of when to prefer the gene-centric sibling, and no prerequisites or caveats about what 'predicted' LOF means for confidence.

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