Skip to main content
Glama

Framezone

by app.framezone
OverviewDiscussionsAdmin

Log workout sets

log_workout_sets

Add exercises and sets to a workout. Accepts gym shorthand ("lateral raise 5kg 4x12", "2min rowing machine") and creates the workout for that date if none exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWorkout type. Sets go to the session of this type on that date; a new session is created when there is none.
notesNoNotes
sets_textYesOne movement per line. Understands "4x12", "40kg", "2dk"/"90sn", "3 set". Example: "lateral raise 5kg 4x12\nincline bench press machine 40kg 4x8"
workout_idNoAdd to this session. Needed when the date holds more than one session of the same type.
workout_dateNoDate (Y-m-d, defaults to today)
allow_duplicatesNoWrite blocks that already exist on that date with the same load and set count. Off by default — a repeated call is far more often a re-send than a second round.
duration_minutesNoSession duration in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Workout type"New value: +"Workout type. Sets go to the session of this type on that date; a new session is created when there is none."
    • addedInput schema / properties / workout_id
      Added value: +{
+  "description": "Add to this session. Needed when the date holds more than one session of the same type.",
+  "type": "integer"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only indicate mutation, so the description usefully reveals a concrete side effect: a workout is created for that date if none exists. It also explains shorthand handling and auto-creation, which are behavioral traits an agent would not infer from readOnlyHint/destructiveHint alone.

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 front-loaded sentences with a useful shorthand example and zero filler. Every clause contributes either the core action, the input format, or the important create-if-none side effect.

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?

The rich schema covers all seven parameters, including examples and edge cases like repeated sessions and duplicate suppression. The description is thin on return behavior, but since there is no output schema and this is a straightforward mutation tool, the combined definition is enough for correct invocation.

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 the schema already explains sets_text, workout_id disambiguation, date defaulting, and allow_duplicates behavior. The description's shorthand mention adds a little flavor but does not materially go beyond the parameter descriptions, so the baseline of 3 is appropriate.

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 clearly states the operation: adding exercises and sets to a workout, with a concise example of accepted gym shorthand. It does not explicitly contrast with sibling tools like log_workout, so the differentiation is implicit rather than stated.

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?

No guidance is given about when to choose this tool over log_workout or delete_workout_sets. The description only states what the tool does; it neither names alternatives nor spells out the conditions under which set-level logging is appropriate.

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

All Framezone toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources