Skip to main content
Glama

add_plan_run

Add a new run workout to a specific week in your training plan by specifying the day, type, distance, and description.

Instructions

    Add a new workout to a week.

    Args:
        plan_id: The plan ID.
        week_number: Which week.
        run_json: JSON string of the run to add.
            Example: {"day_of_week": "Friday", "type": "easy", "distance_km": 8, "description": "Recovery"}

    Returns:
        Confirmation message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYes
run_jsonYes
week_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided. Description only mentions return of confirmation message but does not disclose side effects, authentication needs, or other behavioral traits for a mutation tool.

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?

Description is concise with a docstring-like structure (Args, Returns). Could be more structured but is not verbose. The Returns line is minimal.

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 absence of annotations and low schema coverage, the description covers basic operation but lacks details on error handling, prerequisites, or output format beyond 'Confirmation message'.

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 description coverage is 0%. Description adds meaning by naming parameters (plan_id, week_number, run_json) and provides an example for run_json. Partially compensates for lack of schema descriptions.

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?

Clearly states 'Add a new workout to a week.' Uses specific verb 'add' and resource 'workout to a week'. Distinguishes from sibling tools like remove_plan_run and update_plan_run.

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?

Description implies usage for adding a run to a plan week but lacks explicit when-to-use or when-not-to-use guidance. No mention of alternatives or prerequisites.

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