Skip to main content
Glama

update_coach_memory

Update specific sections of the coach's memory with new athlete information, including goals, training context, injuries, and PRs. Changes are recorded immediately to keep coaching accurate.

Instructions

    Update a specific section of the coach's memory (COACH_MEMORY.md).

    Rewrites the section in-place. Call this immediately when significant
    new information emerges — don't wait until session end.

    Sections:
        athlete — name, location, weight
        prs — self-reported PRs with date assessed
        goals — target race, current phase
        active_flags — injuries, niggles, concerns
        training_context — weekly volume, training days, constraints
        patterns — observations about the athlete's training

    Args:
        section: Section key (athlete, prs, goals, active_flags, training_context, patterns)
        content: New content for the section (replaces everything under the ## header)

    Returns:
        Confirmation message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
sectionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses that the tool rewrites in-place and replaces everything under the ## header. No annotations provided, so description carries full burden. Could mention what happens if section doesn't exist, but schema likely handles validation.

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?

Concise and well-structured: summary line, usage guideline, enumerated sections, parameter explanations. No wasted sentences.

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

Completeness5/5

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

Complete for a simple 2-parameter update tool. Explains purpose, when to use, section options, and parameter behavior. Output schema exists (though not shown), so return value description is sufficient.

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%, but description adds significant value: lists all allowed section values and explains that content replaces everything under the ## header. Compensates well 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?

Clear verb 'update' with specific resource 'coach's memory' and file reference COACH_MEMORY.md. Distinguishes from sibling tools like read_coach_memory.

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?

Explicitly states when to call ('immediately when significant new information emerges — don't wait until session end'). Does not explicitly state when not to use, but the context is clear enough.

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