Skip to main content
Glama

watkins_nil_genes

Read-onlyIdempotent

Genes inside the Watkins introgression of a TK-NIL (Watkins segment in a Paragon background), with presence in the Watkins donor and frequency in modern cultivars and landraces. nil_line is a NIL line name from watkins_population_phenotypes (e.g. 'ParW141_0016-7-10-Q2D-Hd-P'). The interval comes from the NIL name (chromosome-start-end on RefSeq v1.0). Highlights genes the donor lacks but most modern cultivars carry, and genes the donor carries but most modern cultivars lack (Paragon itself is not in the pangenome).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
nil_lineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower, and the description still adds real content: the interval is not a parameter but is derived from the NIL name (chromosome-start-end on RefSeq v1.0), and Paragon itself is absent from the pangenome, which is a genuine coverage caveat. It stops short of describing result ordering or how frequency values are computed.

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?

Roughly four sentences, front-loaded with what the tool returns, then input provenance, then the highlight semantics. Dense domain jargon is unavoidable here; the final parenthetical about Paragon is worth its space as a caveat, though the structure could be tightened.

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 work of explaining what comes back: donor presence, cultivar and landrace frequency, and the two highlight categories (donor-absent/cultivar-common and donor-present/cultivar-rare). The remaining gap is the unexplained limit parameter and any indication of what a result record looks like.

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 carries the burden: it fully explains nil_line's expected format, source, and how the genomic interval is derived from it. The second parameter, limit (default 300), is never mentioned, so truncation and pagination behavior remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope: the genes inside the Watkins introgression interval of a TK-NIL, annotated with donor presence and modern-cultivar/landrace frequency. It also implicitly separates itself from generic lookups (watkins_find_genes, watkins_trait_genes) by tying the query to a NIL-derived interval rather than arbitrary gene search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete prerequisite and provenance rule: nil_line must be a NIL line name obtained from watkins_population_phenotypes, with a literal example. That is strong context, but there is no explicit when-not-to-use statement or named alternative for the general gene-presence case.

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