Skip to main content
Glama

log_rounds_workout

Log a multi-movement 'rounds' For Time workout result to BTWB, with several movements per round across multiple sections and total elapsed time.

Instructions

Log a multi-movement 'rounds' result (e.g. a For Time WOD with several movements per round) to BTWB - as opposed to log_workout, which only handles a single movement. Only 'For Time' workouts scored by total time are supported (other scoring types like AMRAP/total-reps are untested). workoutId/workoutSlug come from the workout's URL (beyondthewhiteboard.com/workouts/{workoutId}-{workoutSlug}/...). Every entry logged through this tool is always posted with Privacy: Only Me - this is hardcoded and cannot be overridden.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rxdYestrue = As Prescribed (Rx'd), false = Modified/scaled
notesNoOptional notes for the entry
memberIdYesBTWB member/profile ID the result is logged under
sectionsYesOrdered list of round groups making up the workout, e.g. a single buy-in round followed by N rounds of several movements.
workoutIdYesNumeric workout ID from the workout's URL
workoutSlugYesURL slug from the workout's URL, e.g. 'ft-rows-9x-toes-to-bars-power-cleans-and-wall-balls'
trackEventIdNoOptional track_event ID to link this result to a scheduled/prescribed WOD (from get_workout_session or the workout's tracks page URL).
performedDateYesDate performed, format YYYY-MM-DD
totalTimeSecondsYesTotal elapsed time in seconds (e.g. hit a 36:00 time cap -> 2160)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses a significant non-obvious behavior: 'Every entry logged through this tool is always posted with Privacy: Only Me - this is hardcoded and cannot be overridden.' That is exactly the kind of side effect an agent must know before writing. Gaps remain around auth requirements, error/failure behavior, and whether results are retrievable after logging.

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?

Front-loaded with the core action and the sibling contrast in the first sentence; the remaining sentences each carry a distinct constraint (supported scoring type, ID derivation, hardcoded privacy). Dense with parentheticals but no filler sentences.

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 9-parameter write tool with no annotations and no output schema, this covers purpose, routing, scoring-type limits, ID provenance, and the privacy side effect. Absent details are the response shape (no confirmation of a created entry ID) and failure/permission behavior, which are minor for this operation.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains the composite workoutId/workoutSlug URL pattern, gives a concrete units example for totalTimeSeconds (36:00 cap -> 2160), and clarifies that 'sections' models an ordered buy-in-plus-rounds structure. It stops short of explaining edge cases like partial rounds or time-cap semantics.

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?

States a specific verb and resource ('Log a multi-movement rounds result ... to BTWB') and immediately differentiates from the sibling log_workout by scoping ('as opposed to log_workout, which only handles a single movement'). An agent can route between the two logging tools without opening either schema.

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

Usage Guidelines5/5

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

Explicitly gives the selection condition against the alternative (multi-movement rounds vs single movement), plus a hard exclusion ('Only For Time workouts scored by total time are supported; AMRAP/total-reps are untested'). It also says where workoutId/workoutSlug come from, which is prerequisite info for calling it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.