openGym MCP Bridge

search_exercises

Search the official openGym exercise catalogue to find valid exercise IDs before creating a routine. Query by name and limit results to get the exact IDs you need.

Instructions

Read-only. Search the official openGym exercise-name catalogue for valid exercise IDs before creating a routine. If the catalogue is not loaded, run node src/catalogue.mjs inside the Bridge container first.

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": {
      "query": "<query>"
    },
    "name": "search_exercises"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations exist, so the description must carry the safety profile — and it does, opening with 'Read-only'. It also discloses a real prerequisite (catalogue must be loaded) with a concrete remediation step. It does not say what a match looks like or how limit truncates results, which keeps it below 5.

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 short sentences, front-loaded with the read-only flag, then purpose, then prerequisite. Every sentence carries distinct information and nothing is repeated from the schema.

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 simple two-parameter search with no output schema, the definition covers what the tool is, why to call it, and the failure mode when the catalogue is missing. It leaves match semantics and result shape unspecified, which is a minor but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, so the description must compensate and does not. Neither 'query' (substring vs fuzzy matching, name-only?) nor 'limit' (default 15, max 30) is explained beyond what the bare schema already shows.

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 ('Search the official openGym exercise-name catalogue') and the value it returns ('valid exercise IDs'). The word 'official' implicitly separates it from list_custom_exercises, but no sibling is named explicitly.

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?

Gives a clear trigger: call this 'before creating a routine' to obtain valid IDs. It also supplies an operational fallback (run node src/catalogue.mjs in the Bridge container) if the catalogue is not loaded. There is no explicit 'when not to use' or named alternative, so it stops short of a 5.

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