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 (['aegilops_tauschii', 'triticum_turgidum', 'hordeum_vulgare', 'brachypodium_distachyon', 'oryza_sativa']). 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds real value with the 500-ID batch ceiling and the note that the web page runs the same call and downloads a TSV, but it says nothing about how unresolvable IDs or partial failures are handled in a batch.

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 capacity limit, followed by a usage hint and the web-page analogue. The inline genome list and odd line break make the first sentence dense, but no sentence is filler.

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 enumerates the returned annotation fields, and it covers capacity limits and the human-facing equivalent. Remaining gaps are minor: no indication of response format, unmapped-gene handling, or response size for a 500-gene batch.

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. It partially does: 'genes' is stated to accept IDs or names up to 500, and the bracketed list of five genomes clearly corresponds to the otherwise opaque 'targets' parameter. However, 'targets' is never named or defined as a parameter, and the accepted format for genome names is left implicit.

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 specific verb and resource ('Annotate a list of genes') and enumerates exactly what the annotation contains: resolved ID, species, location, name, InterPro/Pfam domains, GO terms, Plant Reactome pathways and orthologues. The explicit 'list ... in one call' framing separates it in spirit from single-gene tools like resolve_gene, though no sibling is named outright.

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?

It gives a clear use context: 'For gene-list follow-up after an experiment (DE genes, GWAS candidates)', which tells the agent which scenarios select this tool. It stops short of naming alternatives (e.g. resolve_gene for a single ID) or stating when not to use it.

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