Skip to main content
Glama

update_my_transformations

Replace the coach's own public before/after client transformation gallery (confirm-gated). Sends the full list — read get_my_profile first if only adding one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transformations": "<transformations>"
    },
    "name": "update_my_transformations"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
transformationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only flag it as a non-read-only, non-open-world write. The description adds the crucial behavioral fact that this is a full-list replacement, not a merge, plus that execution is confirm-gated — the two things an agent most needs to avoid clobbering data. Note the mild tension with destructiveHint=false, since 'Replace' overwrites an existing gallery, but the description's explicit full-list warning mitigates rather than contradicts it.

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?

Two short sentences, the destructive replacement semantics front-loaded, and the prerequisite read placed where it is actionable. No filler.

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

Completeness4/5

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

For a two-parameter write tool with no output schema, the definition covers purpose, overwrite risk, and the prerequisite read. Return behavior for the preview path is handled in the schema rather than the description, which is acceptable; entry-level field requirements live in the schema and need no repetition.

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 coverage is 50%, and the description adds no meaning about the 'transformations' array items beyond the schema's required-field list; the confirm-gating it mentions is already documented in the schema's own confirm description. Baseline 3 is appropriate since the schema carries the structural detail.

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 ('Replace the coach's own public before/after client transformation gallery') with explicit scope ('the coach's own public'). The replacement semantics distinguish it from the sibling get_my_profile, which is named directly.

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?

Gives a concrete prerequisite path: 'read get_my_profile first if only adding one,' which tells the agent exactly when a different call is needed first. It doesn't spell out any when-not conditions (e.g., preview-only flows), but the single alternative is routed clearly.

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.