Skip to main content
Glama

Bodywise Fitness Coach

Rest between sets

rest_between_sets_calculator
Read-onlyIdempotent

A rest window in seconds for an exercise type and goal, with the evidence caveats. Not a proven optimum.

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": {
      "exercise_type": "<exercise_type>"
    },
    "name": "rest_between_sets_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoTraining goal.muscle
exercise_typeYesExercise type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine epistemic context beyond them: the result carries 'evidence caveats' and is 'not a proven optimum,' which tells the agent how much authority to grant the returned number.

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 short sentences, front-loaded with the output and inputs and ending with the caveat. Every clause earns its place; nothing is redundant with the schema or annotations.

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, no-output-schema calculator, the description states the return shape (seconds) and its reliability caveat, which is enough for correct invocation. Minor gaps remain around the valid range or interpretation of the returned window, but the core is complete.

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 description coverage is 100% and both parameters have enums documented in the schema, so the baseline of 3 applies. The description restates the same two inputs (exercise type, goal) without adding format, default, or enum-value guidance beyond what the schema provides.

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 names a specific output (a rest window in seconds) and its two inputs (exercise type, goal), so the agent knows exactly what this tool computes. It does not differentiate itself from the ~30 sibling calculators beyond the implicit name, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives (e.g. rpe_rir_calculator, double_progression_calculator) or prerequisites for calling it. Usage must be inferred entirely from the name and output description.

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