Skip to main content
Glama

watkins_gene_accessions

Read-onlyIdempotent

Watkins accessions that carry (present=True) or lack (present=False) a gene, optionally filtered by country, continent, ancestral_group (AG1-AG7 or Modern) or growth_habit. Returns metadata, coordinates and Seedstor ordering links.

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_gene_accessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
limitNo
offsetNo
countryNo
presentNo
continentNo
growth_habitNo
ancestral_groupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds genuine context by disclosing the payload ('metadata, coordinates and Seedstor ordering links'), which is not inferable from the schema. It omits pagination behavior despite limit/offset parameters existing, so it adds value but not full behavioral context.

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?

Two sentences, no filler, with the core selection criterion (carry vs lack a gene) front-loaded before the optional filters. It is dense but readable; the only cost is that pagination and the required gene parameter are absent from otherwise tight prose.

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 correctly supplies a summary of returned fields, and it covers the domain-specific value range for ancestral_group. It is complete enough to call correctly except for paging semantics, which matters for an 8-parameter list tool with a default limit of 50.

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 description coverage is 0%, so the description must carry the load, and it does for most filters: present polarity, country, continent, growth_habit, and critically the ancestral_group value space ('AG1-AG7 or Modern'), which the schema does not encode as an enum. limit and offset are never mentioned, leaving two parameters 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 uses a concrete verb and resource ('Watkins accessions that carry or lack a gene') and explains the boolean polarity via present=True/False, so an agent knows exactly what is being retrieved. It does not name or distinguish itself from near siblings such as watkins_gene_presence or watkins_gene_haplotypes, so it stops short of a 5.

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 makes clear this is the tool for gene-presence-by-accession queries and lists the optional narrowing filters. It gives no explicit when-not guidance, no mention of the alternative sibling tools for haplotypes or trait associations, and no note on the default result window.

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