Skip to main content
Glama

Blocks

by zone.blocks
OverviewDiscussionsAdmin

copy_workouts

Copy planned work from one day to other days — the athlete's own Copy/Paste, as a tool. Pass iid to copy ONE scheduled session (from get_plan), or omit it to copy everything planned on that day. Reach for this instead of re-writing the session with plan_workouts whenever they want the SAME thing again — a repeated Tuesday, last week's long ride, the gym session that worked: it carries the exact structure, the note, the context tags and the key star, and it invents nothing. The copies are independent entries — editing one later changes nothing else, and no series links them. A copy ADDS to the target day; to replace what is there, call remove_from_plan for that day first and say so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesthe day(s) to copy TO
iidNocopy just this one workout (iid from get_plan); omit to copy the whole day
whyNoONE line, in the athlete's language: WHY this change — the reason from the conversation ("travel Thu-Fri, long ride moved to Sat", "deload after 3 build weeks"). The athlete's other assistant surface reads it later; without it, it sees only that the plan changed. No health details beyond what the plan needs.
fromYesthe day to copy FROM

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / why
      Added value: +{
+  "description": "ONE line, in the athlete's language: WHY this change — the reason from the conversation (\"travel Thu-Fri, long ride moved to Sat\", \"deload after 3 build weeks\"). The athlete's other assistant surface reads it later; without it, it sees only that the plan changed. No health details beyond what the plan needs.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With annotations only covering the safety profile, the description supplies the crucial operational semantics: copies are independent entries, no series links them, and a copy ADDS to the target day rather than replacing it. It also notes what is carried over (structure, note, tags, key star) and that nothing is invented.

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 iid behavior, then the usage guidance, then the add-not-replace caveat. It is dense with em-dashes and examples, so it runs slightly long, but every sentence carries actionable information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and annotations that only declare the safety profile, the description covers the add-vs-replace behavior, copy independence, what is preserved, and when to choose this over plan_workouts. An agent has everything needed to call it correctly.

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% and the schema already documents iid, from, to, and why. The description reinforces the key iid distinction (pass it for ONE session from get_plan, omit to copy the whole day), adding a little framing beyond the schema but no new format or syntax detail.

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+resource (copy planned work from one day to other days) and immediately frames it as the athlete's own Copy/Paste. It differentiates from siblings by naming plan_workouts and remove_from_plan as the alternatives for different intentions.

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 says to reach for this instead of re-writing with plan_workouts when the athlete wants the SAME thing again, and gives the replace-vs-add rule (call remove_from_plan first). Concrete scenarios (repeated Tuesday, last week's long ride, gym session) make the selection condition unambiguous.

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

All Blocks 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