Skip to main content
Glama

List thank-yous

list-thank-yous
Read-onlyIdempotent

After the wedding: per invitation what they gave and whether the thank-you card went out, with the postal address for the card. By default the invitations that said yes to a moment (they came) and still need thanking; use filter and everyone to see more. Note a gift or a sent card with update-thank-you.

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": "list-thank-yous"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNotodo (default): not thanked yet; done: card sent; all.
searchNoPart of a name or a gift.
everyoneNoAlso invitations that did not say yes to any moment; they may still have sent something.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the result set is filtered by default to attending invitations that still need thanking, which an agent could not infer from annotations. It stops short of describing ordering or volume of results.

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 compact sentences: what it returns, what the default scope is, and where writes go. Purpose is front-loaded and nothing is redundant, though the opening 'After the wedding:' qualifier is slightly cryptic and the middle sentence packs default scope and override guidance together.

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?

There is no output schema, so the description must convey the return shape, and it does (gift, card status, postal address). For a 3-parameter read-only list tool with full schema coverage and annotations, no call-critical information is missing.

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 100%, so the baseline is 3, but the description goes beyond the schema by explaining the relationship between the default scope and the filter/everyone parameters ('use filter and everyone to see more'). It does not restate the enum values, which the schema already carries.

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?

The description names the resource (thank-yous, per invitation) and the exact payload returned: what was given, whether the card went out, and the postal address. It also implicitly separates itself from the mutating sibling by closing with 'Note a gift or a sent card with update-thank-you.'

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?

It states the default scope explicitly ('invitations that said yes to a moment ... and still need thanking') and tells the agent exactly how to widen it ('use filter and everyone to see more'). It also routes write operations to update-thank-you, so the when-not/alternative case is covered.

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