Skip to main content
Glama

Tribute Paper

Get a design

get_design
Read-onlyIdempotent

Details of one Tribute Paper design by its slug (from search_designs): what it is for, its faith or tradition, style, pages, music, whether it has a place for a photo, every size it comes in (phone card, 5 × 7 print card, square, and folded program booklet on US Letter or order of service on A4), what's included, its page link and similar designs.

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": {
      "slug": "<slug>"
    },
    "name": "get_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe design's slug, e.g. garden-of-grace-funeral-service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is fully covered by structured data. The description's added value is the return-content inventory, which matters because no output schema exists, but it says nothing about unknown-slug behavior or whether missing attributes are omitted vs. null. Useful, though not rich beyond the annotation baseline.

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?

Single front-loaded sentence that leads with the core action before listing returned fields. The size enumeration (phone card, 5 × 7, square, folded program on US Letter/A4) is the densest part and is arguably more detail than needed to decide whether to call, but it is genuinely part of the payload description and not filler.

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?

With one required parameter, full schema coverage, and no output schema, the description correctly carries the burden of describing return values and does so comprehensively. The only gap is failure/edge behavior for nonexistent slugs, which is minor for a low-complexity read tool.

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% and the slug pattern/example is already documented, so the baseline would be 3. The description adds origin information the schema lacks — that the slug is obtained from search_designs — which meaningfully helps the agent construct a valid call rather than guess one.

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?

Opens with a specific verb and resource ("Details of one Tribute Paper design by its slug") and then enumerates the exact content of the record — purpose, tradition, style, pages, music, photo capability, sizes, inclusions, link, similar designs. That inventory distinguishes it cleanly from search_designs, which returns multiple designs rather than one.

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?

The parenthetical "(from search_designs)" tells the agent where the required slug comes from, which effectively routes it to the sibling for discovery before this lookup. It stops short of explicit when-not-to-use guidance or stating what happens if the slug is invalid or stale.

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