Skip to main content
Glama

Update thank-you

update-thank-you
DestructiveIdempotent

Notes what an invitation gave, and whether their thank-you card was sent (today) or not after all. Only the fields you pass change; an empty gift clears it. The logbook records that someone was thanked, never what they gave.

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": {
      "id": "<id>"
    },
    "name": "update-thank-you"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe invitation, from list-thank-yous or search-guests.
giftNoWhat they gave, in the couple's words, e.g. "Vaas en een kaartje".
thankedNotrue: the thank-you card was sent; false: not sent after all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description adds genuinely useful context beyond the annotations: partial-update semantics ('only the fields you pass change'), the fact that an empty gift clears it (explaining the destructiveHint), and the privacy note that the logbook never records the gift itself. It does not state what happens to unspecified fields beyond that, nor confirm the idempotent behavior that the annotations claim.

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?

Three short sentences, each carrying distinct information: target fields, partial-update rule, and the logging caveat. The opening clause is slightly convoluted with the parenthetical '(today) or not after all', but nothing is padding.

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 3-parameter mutation with no output schema, the description covers the update semantics, the clearing behavior, and a privacy caveat that would otherwise surprise an agent. What it lacks is any guidance on choosing this tool over list-thank-yous or sibling updates, a gap that matters more than return-value detail here.

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 100%, so all three parameters are already documented, and the description's 'empty gift clears it' is the main addition over the schema's own wording. The '(today) or not after all' phrasing loosely glosses the boolean but is vaguer than the schema's explicit true/false definitions, so it does not meaningfully outperform the baseline.

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?

The description says the tool notes a gift and the thank-you card status for an invitation, which pins down the resource and the two updatable fields well enough to act on. It never uses the word 'update' or name a sibling, so the distinction from list-thank-yous rests on the schema's 'id' hint rather than the description itself.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus list-thank-yous or the other update-* siblings, and no prerequisites or exclusions. The only routing cue, 'from list-thank-yous or search-guests', lives in the schema parameter text, not the description.

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