Skip to main content
Glama
Sign In

Rhea

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Reaction

get_reaction
Read-onlyIdempotent

Fetch a single Rhea reaction by its Rhea id (e.g. "RHEA:14293" or "14293"). Returns the balanced plain-text equation plus EC number, ChEBI compound, UniProt enzyme and PubMed cross-references. Rhea is the expert-curated biochemical reaction reference used by UniProt and KEGG. Keyless.

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": {
      "id": "RHEA:14293"
    },
    "name": "get_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA Rhea reaction id, e.g. "RHEA:14293" or "14293".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "RHEA:14293"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate safe read-only, idempotent behavior. Description adds valuable return content details (equation, cross-references) and notes it is 'Keyless' (no auth). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, front-loaded with action and resource, no wasted words. Efficient and clear.

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, but description lists key return fields (equation, EC, ChEBI, etc.), compensating well. Could mention pagination or error hints, but sufficient for a single-param fetch.

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 covers 100% of parameter description; description repeats id examples without adding new semantic details. Baseline 3 is appropriate.

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?

Description clearly states the action ('Fetch a single Rhea reaction') and resource ('by its Rhea id'), with example formats. Distinguishes from sibling tools like search_reactions.

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?

Implied use for single reaction lookup, but no explicit when-not-to-use or alternative recommendations (e.g., for searches). Adequate for a simple fetch tool.

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

All Rhea toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources