Skip to main content
Glama

pathway_genes

Read-onlyIdempotent

Genes in a Plant Reactome pathway: pathway is a name or words from it ('jasmonic acid biosynthesis', 'gibberellin', 'flavonoid') or a stable ID (R-TAE-1119332). species: a species name as Plant Reactome writes it ('Triticum aestivum', 'Brassica napus', 'Glycine max'); default all species loaded for this site. Matching pathways are listed with their genes per species. Membership is projected from rice by orthology.

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": {
      "pathway": "<pathway>"
    },
    "name": "pathway_genes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
pathwayYes
speciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavioral context—'matching pathways are listed' (i.e., partial/fuzzy matches can return multiple pathways) and 'membership is projected from rice by orthology' (a caveat about result provenance)—but says nothing about result size, the limit cap, or truncation behavior.

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 purpose, then the two parameters, then two short behavioral notes—each sentence earns its place. The parenthetical example lists are dense and the sentence structure is a run-on chain of clauses, but no filler is present.

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?

For a read-only lookup with no output schema and no nested objects, the description covers purpose, both user-facing parameter formats, species defaulting, and the orthology-projection caveat. The remaining gap is the undocumented 'limit' parameter and silent handling of very large gene sets, which matters for a query that can legitimately return hundreds of genes.

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 description coverage is 0%, so the description carries the full burden and largely succeeds: it defines 'pathway' with accepted syntax and three concrete examples, and defines 'species' with the exact naming convention required plus the null default. The third parameter, 'limit' (default 200), is never mentioned, leaving one of three parameters undocumented anywhere.

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+resource combination ('Genes in a Plant Reactome pathway') with concrete input forms—keyword fragments or stable IDs like R-TAE-1119332. The purpose is unambiguous, but it never distinguishes itself from the inverse-looking sibling gene_pathways, so an agent must infer the direction of the lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it makes clear you supply a pathway name/ID and receive genes, and it notes the species default is 'all species loaded for this site'. There is no explicit when-to-use, no when-not-to-use, and no named alternative for the gene→pathway direction.

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