Stampa e Stampe

Search catalog

search_catalog

Read-only

Searches print products by keyword (e.g. "biglietti da visita", "adesivi trasparenti", "roll up"). The catalog is in Italian and Italian words work best; plurals, some typos and the most common English words (stickers, business cards, flyers) are understood, words that match no product are dropped, and a query_relaxed message lists the words corrected or ignored. For each product: its materials, each priced at the website's default configuration for the pack named in the variant title (metadata.reference_quantity pieces) with economy shipping, in euro cents VAT included (VAT excluded, as the product page shows it, in metadata.price_excl_vat), excluding shipping, packaging and payment-method fees (e.g. cash on delivery), which the website adds at checkout; product page link, image. The price is not linear in the quantity: use get_product for sizes and options, and price_configuration for the exact price of another quantity.

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": {
      "catalog": "<catalog>"
    },
    "name": "search_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`meta`	No	UCP agent envelope. Optional.
`catalog`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

removedInput schema / properties / catalog / properties / filters

Removed value: -{
-  "description": "Accettati ma non applicati: i risultati sono quelli della sola query, o l'intero catalogo senza query.",
-  "type": "object"
-}

changedInput schema / properties / catalog / properties / pagination / properties / cursor / description

Previous value: -"pagination.cursor della risposta precedente."New value: +"pagination.cursor from the previous response."

changedInput schema / properties / catalog / properties / pagination / properties / limit / description
```
Previous value: -"Al massimo 20 risultati per pagina."New value: +"At most 20 results per page."
```

changedInput schema / properties / catalog / properties / query / description

Previous value: -"Parole da cercare. Serve questa o filters."New value: +"Words to search for."

addedInput schema / properties / catalog / required
```
Added value: +[
+  "query"
+]
```

changedInput schema / properties / meta / description

Previous value: -"Busta UCP dell'agente. Facoltativa."New value: +"UCP agent envelope. Optional."

First observedOct 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld=false, and the description adds substantial behavior: Italian-language matching, plural/typo/English tolerance, dropped unmatched terms, and a query_relaxed message. It also precisely discloses what the returned prices include and exclude (VAT handling, shipping, packaging, cash-on-delivery fees) and that pricing is non-linear.

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?

Front-loaded with purpose and examples, and every clause carries useful information about matching or pricing. The single dense paragraph with semicolon chains is information-rich but could be easier to scan if split into matching, output, and alternatives sections.

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 no output schema, the description fully carries return-value semantics: per-product materials, prices at the default configuration for the named reference quantity, euro cents, VAT treatment, exclusions, product page link, and image. It also covers the relaxation message and when to switch to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, but the description compensates by explaining query semantics in depth: language preference, plural/typo handling, common English equivalents, ignored words, and the query_relaxed feedback. Pagination parameters are left to the schema, which documents them adequately.

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?

States a specific verb (searches) and resource (print products catalog) with concrete Italian examples. It clearly distinguishes itself from get_product and price_configuration, but never mentions lookup_catalog, the remaining sibling, so an agent cannot fully disambiguate search vs lookup from this text alone.

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?

Explicitly routes the agent to get_product for sizes/options and price_configuration for exact prices at other quantities, which is strong alternative guidance. It lacks any when-not-to-use note relative to lookup_catalog, leaving a small gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Stampa e Stampe tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?