Skip to main content
Glama

watkins_gene_presence

Read-onlyIdempotent

Presence/absence of one gene across the 1,038 Watkins pangenome accessions: present count, core/variable, counts by ancestral group (AG1-AG7, Modern), continent and growth habit, UniProt/GO annotation and links. gene: symbol, any IWGSC RefSeq ID, or a pangenome gene-model ID.

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

Input Schema

NameRequiredDescriptionDefault
geneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds real behavioral value by disclosing exactly what the response contains (present count, core/variable classification, breakdowns by ancestral group AG1-AG7/Modern, continent, growth habit, UniProt/GO annotation, links) in the absence of an output schema.

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, no filler. The core scope (presence/absence across 1,038 accessions) is front-loaded, the return fields follow as a compact list that earns its space given there is no output schema, and the identifier rules are appended last.

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?

For a one-parameter read-only aggregation tool, the definition covers scope, accepted identifier formats, and return contents. Minor gaps remain: it does not say how 'core' vs 'variable' is thresholded, nor what happens for an unresolvable or ambiguous gene identifier.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description fully carries the burden — and it does: it specifies that the gene may be given as a symbol, any IWGSC RefSeq ID, or a pangenome gene-model ID. That resolves exactly the ambiguity an agent would face before calling.

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 states a specific computation (presence/absence of a single gene) over a named population (the 1,038 Watkins pangenome accessions) and enumerates the resulting breakdowns. This is clearly distinct from sibling tools like watkins_gene_accessions or watkins_gene_haplotypes, which return per-accession records rather than aggregate presence counts.

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 only implied: the phrase 'Presence/absence ... present count, core/variable' signals this is the summary/aggregation tool, so an agent can infer it should be used when counts rather than accession lists are wanted. However, no explicit when-to-use, when-not, or named alternative (e.g., watkins_gene_accessions for the actual accession list) is provided.

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