Skip to main content
Glama

Tribute Paper

Make a start link

start_design_link
Read-onlyIdempotent

Makes a link that opens Tribute Paper with every design already showing the person's name, dates of birth and passing, and the service date, time, venue and town, the same as the site's "Save your details once and every design shows them". With a design slug it opens that design ready to edit (designing is free; a free sign-in is asked for first). Offer it when the family is ready to make a program or card, using only details they have shared. The details ride in the link's #fragment, so they stay in the family's browser and are not sent to Tribute Paper's server. Give at least one detail.

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

Input Schema

NameRequiredDescriptionDefault
bornNoDate of birth: a year (1938) or a full date (1938-03-03).
diedNoDate of passing: a year (2026) or a full date (2026-11-02).
nameNoTheir full name as it should appear, e.g. Margaret Ellis.
sizeNoOptional, with a design: story (phone card), card (5 × 7 print), square, program (folded booklet, US Letter) or oos (order of service, A4).
townNoThe town or city, e.g. Boston.
venueNoWhere the service is, e.g. St Mary's Church.
designNoOptional: a design to open straight away (from search_designs).
service_dateNoThe service date.
service_timeNoThe service time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that details ride in the URL #fragment and never reach Tribute Paper's server (a privacy property the agent cannot infer), that editing requires a free sign-in, and that designing is free. It also clarifies the non-obvious side effect that no server-side record is created, consistent with readOnlyHint=true.

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 core capability is front-loaded and the sentences are dense with information. Some wording is decorative, notably the quoted site slogan ('Save your details once and every design shows them'), which adds length without adding meaning the agent can act on.

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?

No output schema exists, but the description makes clear the return value is a link and explains its contents and privacy behavior. Minor gaps remain: it does not say what the link opens when no design slug is supplied (presumably a design gallery), nor anything about link size or longevity.

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 adds a constraint not encoded in the schema: despite zero required parameters, 'Give at least one detail' must hold. It also explains that supplying a design slug changes behavior beyond simply filling a field — the link opens that design for editing.

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?

States a specific verb and artifact ('Makes a link') and describes precisely what the link opens: a Tribute Paper design prefilled with name, dates, service details, and optionally a specific design ready to edit. An agent can distinguish this from read-only siblings such as search_designs or get_design without opening the schema.

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?

Gives an explicit trigger condition ('Offer it when the family is ready to make a program or card'), a data-handling constraint ('using only details they have shared'), and a prerequisite ('a free sign-in is asked for first'). It does not state when not to use it or name a sibling alternative beyond implying search_designs as the source of a design slug.

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