Skip to main content
Glama

update_my_testimonials

Replace the coach's own public client testimonials (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": {
      "testimonials": "<testimonials>"
    },
    "name": "update_my_testimonials"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations only declare that this is a non-read, non-open-world, non-destructive write. The description adds the crucial behavior the annotation does not capture: the payload is a full-list replacement, so testimonials omitted from the array are effectively lost, and confirm must be set or the call is a preview. That is real added context for a mutation tool. One residual tension: full-list replacement overwrites prior entries, which sits uneasily with destructiveHint=false, even though it is an overwrite rather than a resource deletion.

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 sentences, no filler, and the destructive full-replace semantic is front-loaded before the read-first caveat. Every clause changes how an agent would call the tool.

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 mutation with no output schema, the description plus schema gives enough to call it correctly: preview versus execute is defined and the full-list requirement is stated. Minor gaps remain around the preview response shape and the handling of an empty list.

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 coverage is only 50%, and the confirm parameter is documented inside the schema. The description compensates for the undocumented testimonials parameter by making clear it must be the complete list, which tells the agent every item needs clientName, profileImage and note rather than a delta. It does not describe item ordering or how duplicates are handled.

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?

Specific verb plus resource: 'Replace the coach's own public client testimonials'. It also resolves the ambiguity implied by the 'update_' name prefix by stating the operation is a full replacement, and it separates the write path from the read path by pointing at get_my_profile.

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?

It states the operative condition clearly: if you are only adding one testimonial, read get_my_profile first and reuse the existing list rather than calling this blind. It also flags the confirm gate. What it lacks is an explicit when-not-to-use case (for example, whether removing all testimonials is supported by passing an empty array).

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.