Skip to main content
Glama

gene_pathways

Read-onlyIdempotent

Plant Reactome metabolic and signalling pathways of a gene (Gramene), with the top-level category and a link to the pathway diagram. gene: an Ensembl Plants gene ID or a gene name/symbol. Pathways are projected from rice by orthology, so say they are inferred. Use pathway_genes for the reverse (all genes of a pathway).

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": {
      "gene": "<gene>"
    },
    "name": "gene_pathways"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new context beyond them: the orthology-projection caveat that changes how results should be reported, plus the shape of the response (category + diagram link). It does not mention rate limits or empty-result handling, which keeps it short of a 5.

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 purpose, then parameter meaning, then the orthology caveat, then the alternative tool — a sound ordering with no filler sentences. The prose is telegraphic in places (sentence fragments after the colon), which is efficient but slightly rough.

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?

No output schema exists, and the description compensates by stating what is returned (top-level category and diagram link). Combined with the inference caveat and the reverse-lookup pointer, an agent has enough to call and report results correctly; only minor operational details are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter, so the description must carry the load and does: it explains that 'gene' accepts either an Ensembl Plants gene ID or a gene name/symbol. That is the key ambiguity for this parameter and it is resolved explicitly.

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?

Names a specific verb+resource ('Plant Reactome metabolic and signalling pathways of a gene'), states the data source (Gramene), and specifies the return payload (top-level category plus pathway diagram link). It also distinguishes itself from the sibling pathway_genes by describing that tool as the reverse lookup.

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?

Explicitly routes the agent to pathway_genes for the inverse operation and warns that pathways are orthology-projected from rice so results should be described as inferred. Missing only an exclusion such as non-plant genes or species limits, but the forward/reverse split is clearly drawn.

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