Skip to main content
Glama

search_reactome_entity

Find Reactome stable IDs for pathways, reactions, proteins, and more by keyword search. Filter by species and entity type for precise results.

Instructions

Search the Reactome pathway knowledgebase by keyword (name / fuzzy match).

Resolves a term (pathway / reaction / protein / complex / small-molecule name) to Reactome stable IDs. Matching is keyword/fuzzy — UNLIKE the exact-match ChEMBL search tools, so expect ranked, approximate hits.

RETURNS a dict {'total_count', 'has_more', 'results'} — NOT a bare list. total_count is the number of records RETURNED (capped by limit); has_more is true if more matched beyond the cap. Each result carries 'id' (stable Reactome stId, e.g. "R-HSA-109581"), 'name', 'type' (facet type), 'exactType' (specific BioPAX-ish class), 'species' (list), and — only when include_summation=True — 'summation' (≤240-char description). On upstream failure returns {'error': ...} instead — CHECK FOR 'error' BEFORE READING 'results'.

species and types are validated case-INSENSITIVELY against Reactome's controlled vocabularies and normalized to canonical casing before dispatch: the server-side filter is case-SENSITIVE and silently ignores a mis-cased value (returning UNFILTERED results), so a mis-cased species used to lose most hits. An unrecognized species/type now RAISES rather than silently returning the wrong rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
rowsNoDEPRECATED alias for `limit` (the old name meant per-type rows). Passing both `limit` and `rows` with different values raises.
termNo
limitNoMaximum number of records returned overall (default 25). A true total cap, not per-type.
queryNoSearch string, e.g. "apoptosis", "TP53", "cell cycle". Accepts aliases: `search`, `term`, `keyword`, `keywords`, `search_term`, `name` (supplying two different values raises ValueError).
typesNoFilter by entity type(s), case-insensitive; a string or list. Valid values: Cell, Chemical Compound, Complex, DNA Sequence, Drug, Genes and Transcripts, OtherEntity, Pathway, Polymer, Protein, RNA Sequence, Reaction, Set. Unknown values raise ValueError.
searchNo
keywordNo
speciesNoFilter by species scientific name, case-insensitive (e.g. "Homo sapiens", "homo sapiens", "Mus musculus"). A single string or a list. Unrecognized names raise ValueError (96 species available; see reactome.org/ContentService/data/species/all).
keywordsNo
search_termNo
include_summationNoWhen True, add a ≤240-char 'summation' description to each record. Default False keeps the payload small (a broad default search is ~hundreds of tokens instead of thousands).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses behavior: return dict structure with 'total_count', 'has_more', 'results'; error key on failure; case-insensitivity normalization for species/types with specific validation behavior; and the effect of include_summation on payload size. No contradictions.

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?

The description is verbose but well-structured. It front-loads the main purpose and proceeds logically: behavior, return format, error handling, parameter details. Each sentence adds value, though some repetition (e.g., multiple mentions of return format) could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (12 parameters, no required, output schema exists), the description covers all essential aspects: search behavior, filter validation, return structure, error handling, and parameter aliases. It is complete for an agent to invoke correctly.

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 50%, but the description adds important context beyond the schema: explains the meaning of returned fields, deprecation of 'rows', alias handling for 'query', and the role of 'include_summation'. Some parameters (e.g., 'term', 'search') are aliases but already documented in schema.

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?

The description starts with a clear verb+resource: 'Search the Reactome pathway knowledgebase by keyword (name / fuzzy match).' It distinguishes from sibling tools like ChEMBL search by highlighting fuzzy vs exact match and specifying the domain (pathway knowledgebase).

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?

The description explicitly contrasts with exact-match ChEMBL tools, advising that results are ranked and approximate. It also details return format and error handling, but does not provide explicit when-to-use vs. alternatives beyond the ChEMBL mention, though context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dbcls/togomcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server