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 (['pisum_sativum', 'vicia_faba', 'medicago_truncatula', 'glycine_max', 'phaseolus_vulgaris', 'lupinus_angustifolius']). 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.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description usefully adds the 500-ID batch ceiling, the orthologue target genome set, and the fields returned, but says nothing about behavior for unresolvable IDs, partial failures, or response size.

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?

Front-loaded with the verb and the payload, then a second sentence on the use case and web equivalent. The long genome enumeration is informative but bulky, and the genes.html reference is marginally useful to an API agent.

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 categories so the agent knows what it gets. The remaining gaps are the unexplained 'targets' parameter and no guidance on how results are keyed or paginated, which matters at 500 IDs.

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 the load. It clarifies 'genes' well (IDs or names, up to 500, string-or-array implied) and the parenthetical genome list indirectly maps to 'targets', but the targets parameter is never named or explained, leaving one of two parameters to inference.

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?

States a specific verb (annotate) and resource (a gene list), and enumerates exactly what comes back: resolved ID, species, location, name, InterPro/Pfam domains, GO terms, Reactome pathways and orthologues. The 500-ID batch scope makes it distinguishable from single-gene siblings like find_gene or legume_gene even though no sibling is named.

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?

Gives a concrete use case ('gene-list follow-up after an experiment (DE genes, GWAS candidates)') and clarifies it is the batch analogue of the genes.html gene-list tab. It stops short of naming an alternative tool or stating when to prefer a per-gene lookup instead.

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