Skip to main content
Glama

Reactome Search

reactome_search
Read-onlyIdempotent

Search the Reactome biological pathway database by keyword across all object types (Pathway, Reaction, Protein, Complex, etc.); returns stable IDs and display names grouped by type.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "apoptosis"
    },
    "name": "reactome_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
typesNoComma-sep: Pathway,Reaction,Protein,Complex,...
clusterNoGroup results by type (default true).

Output Schema

NameRequiredDescriptionDefault
entriesNoTotal number of results
resultsNoList of matching objects

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / types / description
      Previous value: -"Comma-sep: Pathway,Reaction,Protein,Complex,…"New value: +"Comma-sep: Pathway,Reaction,Protein,Complex,..."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds that results are grouped by type and return stable IDs and display names, but says nothing about result caps, paging, or how broad keyword matching behaves on this open-world database.

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 sentence that states action, scope, and return in that order with no filler. It could be trimmed slightly, but each clause carries information.

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 rich annotations, an output schema, and two of three parameters documented in the schema, the description covers what an agent needs to invoke it. The only meaningful omission is guidance on choosing between this and the more targeted pathway/entity tools.

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 coverage is 67% and both optional parameters already carry descriptions, so the baseline is a 3. The description reinforces the semantics by enumerating the type values and noting results are grouped by type, but adds no format detail for the query string beyond "keyword" (no tokenization or matching rules).

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 gives a specific verb and resource ("Search the Reactome biological pathway database") plus scope ("across all object types") and a short return summary, so the agent can tell it is a broad keyword search rather than a targeted lookup. It stops short of naming related siblings such as pathway or pathways_for_entity, so differentiation is left to inference.

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?

The phrase "across all object types" implies this is the broad entry point versus narrower tools, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative or prerequisite. Usage must be inferred from the schema examples rather than stated.

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.