Skip to main content
Glama

Tribute Paper

Funeral planning checklist

funeral_planning_checklist
Read-onlyIdempotent

What usually needs doing after a death, in five stages (the first 24 hours, the first few days, planning the service, the day itself, after the service), with short notes for the United States, United Kingdom, Canada or Australia and links to official government pages. General guidance only, not legal advice: the funeral director or local office knows the local rules. Offer it gently, a stage at a time if that's easier.

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": "funeral_planning_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoOnly one stage: first-day (the first 24 hours), first-days (the first few days), planning (planning the service), the-day (the day itself), after (after the service).
countryNoAdds that country's notes and official links: US, GB or UK (United Kingdom), CA, AU.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes further by disclosing content scope (five stages, four supported countries, official-government links), a 'general guidance only, not legal advice' disclaimer, and the deferral to funeral directors/local offices. It does not describe output length or structure, but the tone and liability caveats are valuable additions.

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?

Purpose is front-loaded in the opening clause and every subsequent element — stages, country notes, disclaimer, tone advice — earns its place. It is a single dense run-on sentence rather than being broken into scannable parts, which slightly hurts readability.

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 simple, annotation-covered, two-optional-enum tool with no output schema, the description supplies enough: what the content covers, which countries are supported, what the output contains (notes and links), and the legal caveat. Only the default behavior when no parameters are supplied is left to inference.

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 both enums already document their own values, so the description adds little beyond restating the five stages and the four countries. It implies that omitting stage returns the whole checklist, but never states this explicitly.

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 names a concrete deliverable — a five-stage checklist of 'what usually needs doing after a death' with country-specific notes and official government links. An agent can immediately tell this is a reference/guidance tool rather than a writer like write_eulogy or write_obituary, though it never explicitly distinguishes itself from those siblings.

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 gives real invocation guidance: present the content gently, and fetch one stage at a time via the stage parameter if that suits the user better. There are no explicit when-not-to-use conditions or named alternatives, but the context for calling it is clear.

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