Skip to main content
Glama

genes_with_annotation

Read-onlyIdempotent

Find genes by function: GO term, InterPro or Pfam domain (accession or words, e.g. 'NB-ARC', 'IPR002182', 'GO:0009414', 'disease resistance', 'MADS-box') or Plant Reactome pathway ('gibberellin biosynthesis', R-TAE-...; kind='pathway'). kind: GO, InterPro, Pfam or pathway (default: GO + InterPro + Pfam). Optional species (Ensembl name) and region (chromosome, start, end in bp on the Ensembl/RefSeq v1.0 assembly) filters, e.g. all NLR genes in a QTL interval. Returns matching genes with location, matched terms and genome browser link, plus facet counts by species, chromosome and term. Annotations are electronic (InterProScan, GO from InterPro2GO).

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": {
      "term": "<term>"
    },
    "name": "genes_with_annotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
kindNo
termYes
limitNo
startNo
speciesNo
chromosomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the description's added value is in describing the response: matching genes with location, matched terms, a genome browser link, and facet counts by species, chromosome and term. It also discloses the important caveat that annotations are electronic (InterProScan, InterPro2GO), which qualifies reliability of matches. It does not discuss result capping or pagination behavior when many genes match.

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?

A single front-loaded paragraph that opens with the core action and then supplies parameter and return detail without filler sentences. It is dense — several distinct facts are packed into parentheticals — but every clause carries information an agent needs.

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 seven parameters, no output schema and no schema descriptions, the definition does the heavy lifting: it explains coordinate units and assembly version, the kind defaults, the return payload and facet counts. The main residual gap is limit/truncation behavior, which matters for a tool whose default caps results at 200.

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 does so well for six of seven parameters, spelling out accepted term formats, the kind enum values and default (GO + InterPro + Pfam), Ensembl species naming, and start/end in bp on the v1.0 assembly. The limit parameter (default 200) is never mentioned, leaving one parameter's semantics and any result-cap behavior undocumented.

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?

States a specific verb and resource ('Find genes by function') and enumerates the annotation systems covered (GO, InterPro, Pfam, Plant Reactome pathway) with concrete term examples such as 'GO:0009414' and 'IPR002182'. An agent can tell this is the function-driven gene search tool, but no sibling is named to contrast with near-neighbours like annotate_genes, pathway_genes or genes_in_region.

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?

Clearly signals when to reach for it: looking up genes by functional annotation term, optionally narrowed by species or genomic interval, with a worked example ('all NLR genes in a QTL interval'). It stops short of exclusions or explicit routing to alternatives such as genes_in_region for pure interval queries or pathway_genes for pathway-only lookups.

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