Skip to main content
Glama

search_reactome_entity

Read-only

Search the Reactome knowledgebase by keyword to find pathways, reactions, proteins, and small molecules, returning ranked matches with stable IDs, entity types, and species filters.

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?

Even though annotations already mark readOnlyHint and openWorldHint, the description adds substantial behavioral detail: the exact return dict shape, 'has_more' semantics, error dict on upstream failure, include_summation payload tradeoff, and server-side case-sensitivity normalization. No annotation contradiction exists.

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 longer than typical but every sentence carries meaningful operational guidance, with clear warnings and structured paragraphs. It is front-loaded with the core purpose and avoids filler, though a few details repeat schema descriptions.

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?

For a 12-parameter fuzzy search tool with an output schema and read-only annotations, the description covers the return contract, error handling, filter normalization, and payload optimization. An agent has enough information to invoke it correctly and interpret results without significant gaps.

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 50%, so the description must compensate, and it does by clarifying limit as a total cap, return format, and the species/types validation-to-casing behavior. Some parameters (name, term, search, keyword) remain undocumented outside the schema's query alias note, so it stops short of a 5.

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 opens with 'Search the Reactome pathway knowledgebase by keyword (name / fuzzy match)' and explicitly says it resolves terms to Reactome stable IDs. This is a specific verb+resource with clear scope, and it distinguishes itself from the exact-match ChEMBL search tools.

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

Usage Guidelines5/5

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

It provides direct usage context by contrasting keyword/fuzzy matching with the exact-match ChEMBL search tools, telling the agent when approximate ranked hits are expected. It also warns about case-sensitivity and error-checking behavior, which supports correct selection and invocation.

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