Skip to main content
Glama

Blocks

by zone.blocks
OverviewDiscussionsAdmin

update_plan_workouts

Destructive

The same kind of edit on MANY scheduled workouts — ONE card instead of one per session; use it for an edit covering more than three sessions. Each edits item is date + iid + the fields that change, each meaning what it means in update_plan_workout. Structure, gym content, sport and the key star: update_plan_workout, one by one. An edit the single tool would refuse is an invalid line on the card; the rest land.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
editsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / edits / items / properties / time
      Added value: +{
+  "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d)?$",
+  "type": "string"
+}
  2. Added

TDQS

Score is being calculated.

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