Skip to main content
Glama

update_plan_run

Modify a specific workout in a training plan by week and day, updating only the provided fields while preserving all others.

Instructions

    Modify a single workout within a week. Surgical edit — only the
    specified fields are changed, everything else is preserved.

    Args:
        plan_id: The plan ID.
        week_number: Which week (1-indexed).
        day_of_week: Day name (e.g. "Tuesday", "Sunday").
        updates_json: JSON string of fields to update.
            Example: {"type": "easy", "distance_km": 10, "description": "Recovery run"}

    Returns:
        Confirmation message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYes
day_of_weekYes
week_numberYes
updates_jsonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It states that only specified fields are changed and everything else is preserved, which adds transparency. However, it does not mention potential side effects, reversibility, or any constraints beyond that.

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?

The description is short and well-structured, with a clear opening sentence, a concise parameter list, and an example. Every piece of information is valuable and front-loaded.

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

Completeness4/5

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

The description covers the core functionality and parameter semantics, and notes the return type. It is adequate for a simple tool but lacks details on validation, error handling, or prerequisites. The presence of an output schema mitigates the need for extensive return value explanation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explicitly listing and explaining all four parameters, including an example for updates_json. This adds meaningful context beyond the schema titles.

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?

The description clearly states the tool modifies a single workout within a week, using specific verbs like 'modify' and 'Surgical edit'. It distinguishes itself from siblings such as add_plan_run, remove_plan_run, and update_plan_week by focusing on editing an existing run without affecting other fields.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives like update_plan_week or add_plan_run. It lacks explicit context on prerequisites or scenarios where this tool is preferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wernerpe/mcpacer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server