Skip to main content
Glama

Blocks

by zone.blocks
OverviewDiscussionsAdmin

remove_from_plan

Destructive

Remove planned work from the calendar: one scheduled workout on date (by iid from get_plan), or every planned workout on that day when iid is omitted. Touches planned entries only — completed activities and the day's notes stay. There is no undo: putting a session back is plan_workouts or copy_workouts. Returns how many entries were removed, or says nothing was planned that day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iidNoone workout's iid; omit to clear every planned workout that 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.
dateYesthe day to remove from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"the day to remove from"
    • addedInput schema / properties / iid / description
      Added value: +"one workout's iid; omit to clear every planned workout that day"
  2. 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"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, it discloses exactly what survives ('completed activities and the day's notes stay'), warns there is no undo, and describes the return value ('how many entries were removed, or nothing was planned'). This is meaningful behavioral context the annotations do not carry.

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?

Three sentences, all front-loaded with the highest-value information first (what it does, what it leaves alone, the irreversibility). No filler or redundancy.

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?

Even without an output schema, the description covers return behavior, destruction scope, irreversibility, and the re-add path. Everything an agent needs to invoke this mutation safely is present.

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 value by telling the agent where `iid` comes from (get_plan) and restating the omit-to-clear semantics. It does not expand on the `why` parameter, which is already documented in the schema.

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 ('remove') and resource ('planned work from the calendar'), then precisely distinguishes the two operating modes: one workout by `iid` versus every workout when `iid` is omitted. It also carves out scope against siblings by declaring 'touches planned entries only,' separating it from activity/note tools.

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

Usage Guidelines4/5

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

Gives clear conditions for the two modes (single vs whole-day) and names the re-add path (get_plan for iid; plan_workouts/copy_workouts to restore). It does not explicitly compare against near-neighbors like update_plan_workout or delete_event, so it stops short of full when-not guidance.

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