Skip to main content
Glama

Tribute Paper

Search designs

search_designs
Read-onlyIdempotent

Search Tribute Paper's designs for funeral programs, order of service booklets, memorial and celebration of life cards, homegoing programs, Catholic funeral Mass booklets, anniversaries, headstone unveilings, death announcements, thank-you cards and pet memorials. Understands everyday words from the US, UK, Canada and Australia ("order of service", "homegoing", "year's mind") and small typos. Filter by kind of service, faith or tradition, style, color, or designs with a photo. Returns each design's name, kind, a short description and its page link. Every design comes in every size, including a folded program booklet. get_design gives one design's full details.

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

Input Schema

NameRequiredDescriptionDefault
colorNoOnly designs with this color.
faithNoOnly designs made for this faith or tradition: any (Non-religious / any), christian (Christian), jewish (Jewish), muslim (Muslim), hindu (Hindu), sikh (Sikh), buddhist (Buddhist), chinese (Chinese).
limitNoHow many results to return (1 to 20, default 8).
queryNoWhat the family is looking for, in their words, e.g. "catholic funeral mass booklet", "celebration of life with photo", "order of service blue". Leave out to list popular designs.
styleNoOnly designs in this style.
categoryNoOnly designs of this kind: funeral-service (Funeral Service), memorial-service (Memorial Service), celebration-of-life (Celebration of Life), homegoing-service (Homegoing Service), funeral-mass (Catholic Funeral Mass), graveside-service (Graveside Service), military-funeral (Military Funeral), first-anniversary (First Anniversary), memorial-mass (Anniversary Mass), headstone-unveiling (Headstone Unveiling), heavenly-birthday (Birthday in Heaven), ashes-scattering (Scattering of Ashes), forty-day-memorial (Forty-Day Memorial), death-announcement (Death Announcement), funeral-thank-you (Funeral Thank-You), pet-memorial (Pet Memorial).
has_photoNotrue: only designs with a place for a photo of the person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds behavior the annotations cannot convey: tolerance for US/UK/CA/AU vocabulary, regional synonyms, and small typos, plus the return shape (name, kind, short description, page link). It also discloses the invariant that every design is offered in every size, including folded booklets, which affects how results should be interpreted.

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?

Structure is good: action and scope first, then matching behavior, then filters, then return values, then the handoff to get_design. The long enumerated category list is dense but justified for a semantic search tool that must recognize synonym-rich vocabulary; a few items could be trimmed without loss.

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?

With seven optional parameters, all enums documented, no required inputs and no output schema, the description fills the remaining gaps by explaining what each result contains and how matching tolerates regional phrasing and typos. An agent can decide to call this tool and interpret its results without further information.

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 four parameters carry enums with per-value explanations, so the schema already does the heavy lifting and baseline 3 applies. The description's "Filter by kind of service, faith or tradition, style, color, or designs with a photo" restates the parameter set, adding only the note that the query field accepts natural-language phrasing from the family — useful but marginal over the schema.

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?

"Search Tribute Paper's designs" gives an explicit verb plus resource, then enumerates the product space (funeral programs, order of service booklets, homegoing programs, pet memorials) so the agent knows the scope of the catalog. It closes by naming the sibling get_design for single-item detail, cleanly separating list-level from detail-level retrieval.

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 description states when to omit the query ("Leave out to list popular designs") and routes the agent to get_design when full details for one design are needed. It does not explicitly state when to prefer the sibling search tool or when filters should be combined versus described in free text, but the primary use context is unambiguous.

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