Skip to main content
Glama

Bodywise Fitness Coach

Lower-fatigue exercise swapper

lower_fatigue_exercise_swapper
Read-onlyIdempotent

Alternatives to heavy compound lifts that train the same muscles with less spinal load, less balancing, less weight or fewer muscles. Mechanical reasons, not measured fatigue scores.

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": {
      "lift": "<lift>"
    },
    "name": "lower_fatigue_exercise_swapper"
  }
}

Input Schema

NameRequiredDescriptionDefault
liftYesLift to swap.
reasonNoWhat you want less of.any

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds one genuinely non-obvious caveat – recommendations are mechanical reasoning, 'not measured fatigue scores' – which prevents the agent from presenting results as quantified fatigue data. It says nothing about how many alternatives come back or in what form, leaving the response shape opaque since no output schema exists.

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?

Two sentences, no filler, with the core framing (alternatives with less demand) front-loaded and the scope caveat second. Every clause carries information.

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 two-parameter, closed-enum, read-only lookup with a fully described schema, the description covers purpose and the key caveat. The remaining gap is the return shape – whether it yields exercise names, a ranked list, or per-alternative rationale – which matters because no output schema exists.

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% with both parameters enumerated and documented, so the baseline would be 3. The description earns above baseline by spelling out the four axes ('less spinal load, less balancing, less weight or fewer muscles') that map directly onto the reason enum values spine/stability/load/muscles, giving the agent a semantic key for choosing a reason.

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?

The description states a specific resource: substitute exercises for heavy compound lifts, qualified by the four axes of reduced demand (spinal load, balancing, weight, muscle count). It implicitly separates itself from search_exercises and muscle_length_exercise_finder by framing the output as 'alternatives' to a named lift. No explicit verb ('returns'/'lists'), which keeps it just short of a 5.

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?

Usage is only implied – an agent can infer this is for a lifter who wants to keep training a movement pattern while reducing a specific stressor. There is no statement of when to prefer this over search_exercises, resistance_profile_explorer, or muscle_length_exercise_finder, and no prerequisites or exclusions.

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