Skip to main content
Glama

watkins_find_genes

Read-onlyIdempotent

Find Watkins pangenome genes by UniProt protein name, gene name, protein family or ID fragment (e.g. 'FAR1', 'NLR', 'Disease resistance protein RGA'). Returns gene IDs with UniProt/GO annotation.

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": {
      "query": "<query>"
    },
    "name": "watkins_find_genes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the return shape ('gene IDs with Uniprot/GO annotation'), which the annotations do not state. It stops short of explaining what happens on no match or how the limit bounds results, so it is strong but not complete.

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 searchable fields and their examples come first, the return value second, so the most decision-relevant information is front-loaded.

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 two-parameter read-only search with no output schema, the definition supplies what an agent needs to call it correctly: the query vocabulary, examples and the returned annotation set, with annotations covering the safety profile. The only real gap is the undocumented 'limit' parameter and default page size.

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 does this well for 'query', naming the four acceptable identifier kinds and giving worked examples, which meaningfully exceeds the bare string type in the schema. The second parameter, 'limit', is never mentioned, leaving half the input undocumented in both places.

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 opens with a specific verb ('Find') and resource ('Watkins pangenome genes'), then enumerates the four searchable fields (UniProt protein name, gene name, protein family, ID fragment) with concrete examples such as 'FAR1', 'NLR', 'Disease resistance protein RGA'. An agent knows exactly what this tool searches. It does not, however, contrast itself with nearby siblings like watkins_trait_genes or watkins_nil_genes, so it falls 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 by the example queries rather than stated: an agent can infer this is the lookup to reach for when it has a protein or gene name and wants annotated gene IDs. There is no explicit when-to-use rule, no exclusion, and no named alternative for the closely related watkins_trait_genes and watkins_nil_genes tools, leaving the routing decision to inference.

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