Skip to main content
Glama

watkins_populations

Read-onlyIdempotent

Paragon x Watkins (and a few Robigus/other x Watkins) RIL populations: Watkins parent, country, ancestral group, number of RILs, GRU seed code, genetic map type and whether it donated TK-NILs. With population (e.g. 'ParW034') or watkins_parent (e.g. 'WATDE0005') also lists the trials in which its lines were phenotyped.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "watkins_populations"
  }
}

Input Schema

NameRequiredDescriptionDefault
populationNo
watkins_parentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 description correctly spends its words elsewhere: it discloses the shape of the payload and the conditional behavior that filtered calls also list trials. It does not mention ordering, pagination, or empty-result behavior, which is a modest gap for a listing tool.

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, dense but well ordered: the resource and its returned fields come first, the filter-dependent behavior second. No filler or restated naming.

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 and no parameter descriptions in the schema, the description supplies the returned-field inventory and filter examples that an agent needs to call it correctly. The only omission is the semantics of combining both filters or passing neither.

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?

With 0% schema description coverage the description must carry the parameters, and it does add real meaning: concrete example values ('ParW034', 'WATDE0005') that reveal expected identifier formats, plus the effect each filter has on the result. It omits how the two filters interact when both are supplied, keeping it below a 5.

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 the resource precisely (Paragon x Watkins and related RIL populations) and enumerates the attributes returned: Watkins parent, country, ancestral group, RIL count, GRU seed code, genetic map type, and TK-NIL donation. This is enough to distinguish it from watkins_population_phenotypes or watkins_accession without opening the schema.

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 description shows that supplying 'population' or 'watkins_parent' enriches the result with phenotyping trials, which hints at when the filter matters. It never says when to prefer this over watkins_population_phenotypes or what happens if neither parameter is passed, so the agent must infer.

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