Skip to main content
Glama

Change my profile

update_profile
DestructiveIdempotent

Changes how they build endurance (mix) or which kettlebells they have. Send only what changes.

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
mixNoWhich endurance sports they do: runner (run), swimmer (swim), rider (ride), rider_runner (run & ride), swimrunner (run & swim), rider_swimmer (swim & ride) or triathlete (run, swim & ride). Sports left out are not trained.
kettlebellsNoHow many kettlebells they own in each weight class, 0 to 2 each. Moderate: get-ups and overhead work. Heavy: swings, squats and presses. Extra heavy: heavy carries. All 0 trains with bodyweight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mix / enum
      Previous value: -[
      -  "runner",
      -  "swimmer",
      -  "rider",
      -  "rider_runner",
      -  "swimrunner",
      -  "rider_swimmer",
      -  "triathlete"
      -]New value: +[
      +  "triathlete",
      +  "runner",
      +  "swimmer",
      +  "rider",
      +  "rider_runner",
      +  "swimrunner",
      +  "rider_swimmer"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / mix / description
      Previous value: -"How they want to build endurance: runner, swimmer, rider, rider_runner, swimrunner, rider_swimmer or triathlete."New value: +"Which endurance sports they do: runner (run), swimmer (swim), rider (ride), rider_runner (run & ride), swimrunner (run & swim), rider_swimmer (swim & ride) or triathlete (run, swim & ride). Sports left out are not trained."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the mutation and safety profile is covered structurally. The description adds the partial-update convention, which is genuine extra context, but it never warns that overwriting kettlebells with zeros removes the trainee's equipment profile — the main destructive consequence flagged by the annotations.

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?

Two short sentences with the purpose stated first and the calling convention second; nothing is padded. The phrasing "how they build endurance (mix)" is slightly oblique versus simply naming the endurance-sport field, but it costs only a few words.

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?

For a two-parameter mutation tool with full schema coverage and no output schema, most of what an agent needs is present. However, "send only what changes" is incomplete for the nested kettlebells object, which requires all three weight classes when supplied, and there is no mention of what a successful response looks like or how to verify the change.

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?

Schema description coverage is 100% and the enum for mix plus the nested kettlebells fields are fully documented in the schema, including the meaning of each weight class and the all-zero bodyweight case. The description only gestures at the two parameter names and adds no format or constraint detail beyond the schema.

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?

Names a specific verb ("Changes") and two concrete resources (endurance mix and kettlebells owned), so the agent knows exactly what domain is being modified. It never names the read counterpart (my_profile), so sibling differentiation is only implied by the read/write split rather than stated.

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?

"Send only what changes" gives a usable rule for how to call it (partial update rather than full replace), which is real guidance. There is no explicit when-to-use vs. alternative statement, no mention of prerequisites, and no note that the read tool should be used first to inspect current values.

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