Skip to main content
Glama

Tribute Paper

Write a eulogy

write_eulogy
Read-onlyIdempotent

Drafts a eulogy from the speaker's own answers, the same as Tribute Paper's free eulogy helper: an opening, who they were, a story, what they taught us, and a goodbye, with how long it takes to read aloud at a calm pace. It never invents memories: everything comes from what the speaker shares. Ask gently for a story and a few words about them first. Needs the relationship and their name or what the speaker called them.

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": {
      "relationship": "<relationship>"
    },
    "name": "write_eulogy"
  }
}

Input Schema

NameRequiredDescriptionDefault
bondNoWhat they were like to the speaker: as a parent, how they met, what it was like to be their grandchild.
nameNoTheir full name, e.g. Harold Brandt.
storyNoOne story that shows who they were, in the speaker's words.
wordsNoA few words that describe them, e.g. "patient, stubborn in the best way, and quietly funny".
regionNoSets the everyday names used when no call_name is given (Mom in the US and Canada, Mum in the UK and Australia): us, ca, uk, au.us
taughtNoWhat they taught the speaker, e.g. "that showing up is most of what love is".
goodbyeNoA last word to them, e.g. "thank you for every mile you drove for us".
pronounNoThe pronoun for the person who died (not needed for a mother or father). Ask rather than guess.
speakerNoThe speaker's own name, to introduce themselves.
call_nameNoWhat the speaker called them, e.g. Mom, Grandpa Hal, Dee. Leave out to use Mom/Mum, Dad, Grandma, Grandpa or their first name.
miss_mostNoWhat the speaker will miss most.
for_familyNotrue when speaking for the whole family ("we") rather than only for themselves ("I").
relationshipYesWho they were to the speaker: mother, father, grandparent, spouse (spouse or partner), friend, other.
speaker_roleNoHow the speaker is related, e.g. "his oldest granddaughter".
who_they_wereNoWho they were: where they grew up, their work, what filled their life. Paragraphs may be separated by blank lines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description still adds real behavioral value beyond them: "It never invents memories: everything comes from what the speaker shares" and the read-aloud-duration note tell the agent about grounding and output form. It stops short of saying what happens when optional sections are omitted or what the returned text looks like.

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?

The first clause states the action immediately and the section list is compact and informative. The comparison "the same as Tribute Paper's free eulogy helper" is promotional filler that does not help tool selection, but the rest of the text earns its place.

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

Completeness3/5

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

For a 15-parameter generation tool with no output schema, the description should say more about the returned artifact. It sketches the section structure and mentions read-aloud length, but an agent still cannot tell how sparse input affects output completeness or whether the result is plain prose, labeled sections, or something else.

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?

With 100% schema description coverage, the schema already documents all 15 fields in detail, so the baseline applies. The description only adds that relationship plus a name or call_name are needed, which is useful but slightly ambiguous about whether name itself is required. Little meaning is added beyond the structured fields.

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?

"Drafts a eulogy from the speaker's own answers" is a specific verb plus resource, and the enumeration of the five sections (opening, who they were, a story, what they taught us, goodbye) pins down the output's scope. It does not, however, distinguish itself from the sibling write_obituary, so an agent cannot tell from this text alone which of the two to choose.

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?

"Ask gently for a story and a few words about them first" gives clear pre-call sequencing advice, and "Needs the relationship and their name or what the speaker called them" states prerequisites. There is no explicit when-not guidance or named alternative among the sibling tools, which keeps it below a 5.

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