Skip to main content
Glama

update_plan_week

Modify weekly focus or planned distance for a specific week in a training plan.

Instructions

    Update week-level metadata (weekly_focus, total_planned_distance_km, etc.).

    Args:
        plan_id: The plan ID.
        week_number: Which week.
        updates_json: JSON string of week-level fields to update.
            Example: {"weekly_focus": "Deload week", "total_planned_distance_km": 50}

    Returns:
        Confirmation message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYes
week_numberYes
updates_jsonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Lacking annotations, the description carries the full burden. It indicates a mutation ('Update') but does not disclose behavior on non-existent weeks, idempotency, permissions, or error conditions. The return value is vague ('Confirmation message').

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 concise and well-structured with an Args section and example. Front-loaded with purpose, no redundant sentences.

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?

Given the output schema exists, the return value is minimally described. However, missing behavioral details (e.g., partial vs full update, error handling) leave gaps for an agent to fully understand consequences.

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?

With 0% schema coverage, the description adds meaning for updates_json via an example but provides no extra details for plan_id or week_number beyond their names. The example is helpful but incomplete for all parameters.

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?

The description clearly states the verb 'Update' and the resource 'week-level metadata', providing specific examples of fields. It differentiates from siblings like update_plan_run by focusing on week metadata, though it doesn't explicitly exclude run-level updates.

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?

No guidance on when to use this tool versus alternatives. It does not specify prerequisites, conditions for use, or cases where another tool (e.g., update_plan_run) would be more appropriate.

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