Skip to main content
Glama

annotate_genes

Read-onlyIdempotent

Annotate a list of genes (up to 500 IDs or names) in one call: resolved ID, species, location, name, top InterPro/Pfam domains, GO terms, Plant Reactome pathways and orthologues in the main related genomes (['brassica_napus', 'brassica_rapa_ro18', 'brassica_oleracea', 'camelina_sativa', 'arabidopsis_thaliana']). For gene-list follow-up after an experiment (DE genes, GWAS candidates); the web page genes.html (gene-list tab) runs this and downloads a TSV.

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": {
      "genes": "<genes>"
    },
    "name": "annotate_genes"
  }
}

Input Schema

NameRequiredDescriptionDefault
genesYes
targetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / targets / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Rich annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false) already establish this as a safe, repeatable, non-mutating lookup, so the description's remaining job is smaller. It usefully adds the 500-ID batch ceiling, the fact that input may be IDs or names (implying resolution of ambiguous names), and the field set returned. It says nothing about what happens to unresolvable or partially matched genes, nor about rate limits or response size for a 500-gene request.

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, front-loaded with the action and the returned fields, then the use case. The genome list and the genes.html web-page reference are slightly bulky, though the latter does clarify the output form (TSV). Little genuine waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 steps in to enumerate the returned annotation fields, which is the most important gap it fills. But for a two-parameter tool it omits one parameter entirely (`targets`) and gives no guidance on batch failure modes or how large a 500-gene response is. Adequate to call it correctly for the common case, incomplete at the edges.

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 must carry parameter meaning — and it only partly does. The `genes` parameter is well served: it accepts up to 500 IDs or names and may be a list. The `targets` parameter is never mentioned; the parenthetical list of genomes ('brassica_napus', 'arabidopsis_thaliana', etc.) hints at what targets controls but never names the parameter or states its default, leaving the agent to guess.

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 and resource ("Annotate a list of genes") and enumerates exactly what each annotation contains: resolved ID, species, location, name, InterPro/Pfam domains, GO terms, Plant Reactome pathways, and orthologues. That distinguishes it from single-query siblings such as find_gene or gene_pathways by making clear it is a bundled batch annotation. It stops short of explicitly naming any sibling it replaces, so 4 rather than 5.

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?

"For gene-list follow-up after an experiment (DE genes, GWAS candidates)" gives a concrete triggering scenario, and "in one call" signals why to batch here rather than call per-gene tools. It offers no explicit when-not or named alternative, which is the only thing separating it from a 5.

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