Skip to main content
Glama

Update the athlete profile

update_profile
Destructive

Updates the athlete's profile: summary and goals replace what's there, addCoachNote appends one note to your running coach notes (for things worth keeping across chats, such as age, height and weight if the athlete shared them). Injuries and the setup answers (profile.intake) can't be changed from here; only the athlete can change them. Rules have their own tools (set_athlete_rule, set_program_rule).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalsNo
summaryNo
addCoachNoteNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

The annotations flag a destructive, non-idempotent, non-read-only mutation, and the description earns its keep by explaining exactly why: `summary` and `goals` overwrite existing content while `addCoachNote` only appends. It also discloses the immutability of injuries and `profile.intake` from this endpoint, which the annotations cannot express. It stops short of saying whether omitted fields are left untouched or cleared, which is the one behavioral detail an agent still 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?

Dense and front-loaded, with the mutation semantics stated before the exclusions and the sibling pointers. The parenthetical about age/height/weight is slightly chatty but supplies concrete guidance on note content, so it justifies its space; overall it is one tight paragraph with no filler.

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?

For a three-optional-parameter mutation with no output schema, the description covers what can be changed, what cannot, and how each field behaves on write. Combined with the destructive annotation, an agent has enough to invoke it correctly and cautiously.

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?

With zero schema description coverage, the description carries the load and does explain the semantics of all three parameters: replace-vs-append behavior and the intended content of a coach note. What it leaves out is that `goals` is an array (each entry presumably a distinct goal) and the per-field length limits that the schema enforces, so an agent could still submit an oversized or malformed value without warning.

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?

States a specific verb and resource ("Updates the athlete's profile") and then defines exactly what each of the three fields does, including the contrast between `summary`/`goals` replacing content and `addCoachNote` appending. It also carves out neighboring territory by naming set_athlete_rule and set_program_rule, so an agent can distinguish this from rule-related mutations without opening any schema.

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

Usage Guidelines5/5

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

Gives both when-to-use guidance (coach notes for "things worth keeping across chats, such as age, height and weight") and explicit when-not-to-use boundaries (injuries and `profile.intake` cannot be changed here). It also routes rule changes to the named sibling tools, so the agent has a clear alternative path rather than having to guess.

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