Stampa e Stampe

Look up products

lookup_catalog

Read-only

Retrieves up to 20 products by product or material id (as returned by search_catalog). Each material reports in inputs the requested id that produced it. A product id returns only the default material of its product page: the others are in options, each with its own id to request here or from get_product.

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

Input Schema

Name	Required	Description	Default
`meta`	No
`catalog`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive and closed-world behavior, so the marginal bar is lower; the description still adds real value by disclosing the 20-item cap, that each returned material echoes the requested id in 'inputs', and that a product id yields only the default material while siblings live in 'options'. Return shape is partially explained, though no output schema exists to confirm the structure.

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?

Three dense sentences with the core capability front-loaded and the id-lineage detail placed where it is needed. Some phrasing ('reports in inputs the requested id that produced it') is awkward but not wasteful.

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?

For a nested, two-parameter read tool with no output schema, the description covers the essential contract: what the ids are, the batch limit, and how product-vs-material results differ. The undisclosed 'meta' envelope parameter is the only meaningful gap.

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 0% with a nested object schema, so the description carries the burden. It explains catalog.ids well (array of product or material ids, max 20, sourced from search_catalog) but says nothing about the optional 'meta.ucp-agent.profile' parameter, leaving one of two parameters undocumented.

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 and resource ('Retrieves up to 20 products by product or material id') and pins the origin of those ids to search_catalog. It does not clearly separate its purpose from get_product, which it only mentions as an alternative source for the same ids.

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 workflow hint that ids come from search_catalog, and it notes a nested id can be requested 'here or from get_product'. There is no explicit statement of when to prefer this tool over get_product or price_configuration, so the agent must infer the routing.

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?