Skip to main content
Glama

Remove a program day

remove_program_day
DestructiveIdempotent

Removes a day from the athlete's program; its weekdays become rest. The week must keep a training day. Forks a preset first (see set_program_day).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dayId": "<dayId>"
    },
    "name": "remove_program_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayIdYes
programNameNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them: the weekdays-turned-rest side effect, the invariant that at least one training day must remain, and the copy-on-write behavior of forking a preset. It stops short of saying what happens to historically logged data for the removed day.

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 short clauses, front-loaded with the action and its effect, followed by the constraint and the preset caveat. No filler and nothing that could be cut.

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

Completeness3/5

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

For a destructive, no-output-schema mutation the description covers the essential behavior and the key invariant, which is more than most. However, with zero parameter documentation and no statement of return value or confirmation behavior, an agent still lacks what it needs to form the correct arguments confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, so the description carries the full burden — and it provides none. It never explains that dayId identifies the day to remove or what programName means (presumably the preset being forked), leaving an agent to guess at the distinction between the two fields.

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 ("Removes a day from the athlete's program") and adds the resulting state ("its weekdays become rest"). This distinguishes it cleanly from set_program_day and set_rest_day without requiring the schema to be opened.

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 a concrete precondition ("The week must keep a training day") that governs whether the call will succeed, plus a pointer to set_program_day for the preset-forking behavior. It does not explicitly contrast with set_rest_day, which is the obvious alternative for making a day non-training, so a small gap remains.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources