Skip to main content
Glama

Tribute Paper

Search Tribute Paper

search
Read-onlyIdempotent

Searches everything on Tribute Paper: designs, funeral readings and poems, the free tools, questions families ask, step-by-step help articles (printing a folded booklet, sharing the page, refunds…), the policies, prices and how it works. Returns a list of results with an id, title and link; fetch gives the full text of one.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. "order of service A4", "poem for a father", "is anything added at checkout".

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the two-step pattern (results carry id/title/link, then fetch retrieves full text), which is genuinely useful workflow context, but it says nothing about result counts, ranking, truncation, or pagination for a search that spans an entire site.

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 scope statement is front-loaded in the first clause, and the second sentence delivers the return shape plus the follow-up action. The parenthetical examples of help articles are somewhat list-heavy but each item clarifies the corpus, so little is wasted.

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 an output schema, full parameter coverage, and rich annotations, the description only needs to convey scope and the retrieve-next pattern, both of which it does. The only real gap is routing guidance among the overlapping specialized search siblings, which matters given the sibling list.

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?

There is a single query parameter with 100% schema description coverage, including concrete examples and a maxLength, so the schema already carries the semantics. The description adds only a broad list of content categories, which loosely signals query vocabulary but no syntax or constraint details beyond the schema.

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 gives a specific verb and a scoped resource, enumerating the corpus types (designs, readings, poems, free tools, help articles, policies, prices) so an agent knows this is a broad site-wide search rather than a narrow one. It partially differentiates from siblings by noting that 'fetch gives the full text of one,' but it does not distinguish itself from search_designs or find_readings, which cover some of the same enumerated content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the search-then-fetch workflow, which tells an agent this is the discovery step and fetch is the retrieval step. However, there is no explicit guidance on when to prefer this over the narrower siblings search_designs or find_readings, so the agent must infer that this is the general fallback.

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