Skip to main content
Glama

Set the program's weekly schedule

set_program_week
DestructiveIdempotent

Sets the whole weekly schedule: each weekday is a day id of the program or "rest", with at least one training day. Forks a preset first.

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": {
      "week": "<week>"
    },
    "name": "set_program_week"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYes
programNameNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructive=true and idempotent=true; the description adds real value beyond them by disclosing the "forks a preset first" side effect and the at-least-one-training-day validation rule. It does not explain what happens to the athlete's existing schedule or day data when it is overwritten, which is the key destructive behavior an agent needs.

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?

Two short sentences, front-loaded with the operation and scope, then the constraint and the prerequisite. No filler, though the "Forks a preset first" fragment reads as an afterthought rather than a structured prerequisite.

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 nested-object, destructive, no-output-schema tool, the description covers the week payload constraint and the fork side effect but omits the fate of the existing schedule and the meaning of programName. Adequate to start a call, incomplete for a safe overwrite.

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 0%, so the description must carry parameter meaning. It does explain the nested week object (weekday keys, day-id or literal "rest" values, minimum one training day) but says nothing about programName — which program is targeted and why it is optional — leaving one of two parameters undocumented.

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?

States a specific verb and resource ("Sets the whole weekly schedule") and names the shape of the payload (weekday -> day id or "rest"). The word "whole" implicitly separates it from per-day setters like set_program_day, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

The scope (whole week vs. single day) implies when to reach for this over set_program_day, and "Forks a preset first" signals an ordering prerequisite. There is no explicit when-not or alternative-tool guidance, so the agent must infer the routing.

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