Skip to main content
Glama

Bodywise Fitness Coach

Weekly sets per muscle

weekly_volume_auditor
Read-onlyIdempotent

Describes weekly hard sets per muscle group against the roughly 10-or-more weekly sets the 2026 ACSM position stand favoured. Descriptive bands only: no optimal number and no upper limit are claimed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "weekly_volume_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
backNoWeekly hard sets, back.
chestNoWeekly hard sets, chest.
quadsNoWeekly hard sets, quads.
bicepsNoWeekly hard sets, biceps.
tricepsNoWeekly hard sets, triceps.
shouldersNoWeekly hard sets, shoulders.
hamstringsNoWeekly hard sets, hamstrings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the bar is lower. The description adds genuine interpretive context by disclaiming that bands are descriptive with no optimal or upper limit claimed, but it does not say what the bands are or how unspecified muscles (defaulted to 0) are handled.

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?

Two tight sentences with the reference standard front-loaded and the caveat following immediately; no filler. Slightly under-specified rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining the return, and it only gestures at 'descriptive bands' without defining the bands or thresholds. Inputs are fully covered by the schema, so the remaining gap is moderate rather than severe.

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 schema already documents all seven muscle parameters, and the description adds no per-parameter meaning beyond the shared notion of 'hard sets'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource and verb: it reports weekly hard sets per muscle group assessed against a stated reference (the ~10+ weekly sets in the 2026 ACSM position stand). It is clearly distinguishable in kind from sibling calculators like double_progression_calculator, though it never explicitly disambiguates itself from them by name.

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 rather than stated: an agent can infer this is for auditing an existing weekly set count, and the description pins the reference standard. However, there is no explicit when-to-use guidance or routing against any of the many sibling calculators (e.g., double_progression, rest_between_sets).

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