Skip to main content
Glama

LiftBrain Library

Find exercise

liftbrain_find_exercise
Read-only

Searches a free catalog of about 870 exercises by English words, e.g. "romanian deadlift" or "cable face pull": the muscles, equipment, level and step-by-step instructions.

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": "liftbrain_find_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesEnglish name or words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds real value beyond them by disclosing catalog size (~870), that access is free, and what each result carries: muscles, equipment, level, and step-by-step instructions — important since there is no output schema.

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?

It is a single front-loaded sentence with no filler. The trailing colon list of returned fields is slightly awkward and could read as a second clause, but nothing is wasted and the key information leads.

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 one-parameter, side-effect-free search tool with no output schema, the description covers the search domain, input style, and result contents well. Minor gaps remain: no indication of how results are ranked or limited despite the large catalog, and no note on behavior for non-English or no-match queries.

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 100% and the single `query` parameter is already documented as "English name or words," so the baseline is 3. The description goes slightly further by supplying realistic multi-word example queries, which clarifies that phrase-style partial matching is expected rather than strict exact-name lookup.

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 gives a specific verb ("Searches"), a concrete resource ("a free catalog of about 870 exercises"), and the input mode ("by English words"), so an agent knows exactly what the tool retrieves. The noun "exercise" vs. the siblings' guide/recipe focus makes the domain boundary unambiguous.

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?

Two worked query examples ("romanian deadlift", "cable face pull") imply the expected usage pattern, but there is no explicit statement of when to use this instead of liftbrain_get_guide or liftbrain_search_recipes. An agent must infer that this tool is for exercise lookup rather than workout/recipe content.

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.

Resources