Skip to main content
Glama

Bodywise Fitness Coach

Deload planner

deload_planner
Read-onlyIdempotent

Whether a planned lighter week (deload) is due from training weeks completed, and what it looks like: same exercises and weights, half the sets (at least one), about four reps in reserve, for one week.

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": {
      "level": "<level>",
      "weeks_since_last_deload": "<weeks_since_last_deload>"
    },
    "name": "deload_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesTraining experience.
exercisesNoOptional exercises and normal working sets, to show deload sets.
weeks_since_last_deloadYesCompleted training weeks in a row since the last lighter week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds genuinely new behavioral content: the computation is a yes/no due-ness judgement plus a concrete deload prescription with specific rules (half sets, minimum one set, ~4 RIR, one week). It stops short of describing the return shape or the threshold rule that decides 'due', which is the one remaining behavioral gap.

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 dense sentence, front-loaded with the core question (is a deload due) before the prescription detail. Every clause carries information, though the nested parentheticals make it slightly harder to scan than a two-sentence split would be.

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?

With no output schema, the description must convey what comes back, and it does: a due/not-due determination plus the deload structure. For a three-parameter read-only calculator this is nearly sufficient; the missing piece is the actual rule that triggers 'due' (e.g. how weeks_since_last_deload interacts with level).

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%, so the baseline is 3 and the schema already documents level, exercises and weeks_since_last_deload. The description does clarify how exercises are used (the deload shows the same exercises at half the sets, minimum one), but that rule is largely restated by the schema's own 'to show deload sets' note. It adds the transformation logic rather than new per-parameter meaning.

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 the specific decision it makes ('whether a planned lighter week (deload) is due from training weeks completed') and the concrete prescription it returns (same exercises/weights, half the sets with a floor of one, ~4 reps in reserve, one week). That is far more specific than a title restatement and clearly separates it from dosing or fuelling planners. It does not explicitly contrast itself with a named sibling, which keeps it just below the top mark.

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 implied by the input concept ('training weeks completed'), so an agent can infer this is the tool for deciding on a deload week. However, there is no explicit when-to-use statement, no when-not-to-use condition, and no pointer to any alternative planner. Guidance is inferable rather than stated.

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