Stampa e Stampe

Product details

get_product

Read-only

Product details by product or material id. Besides the UCP fields, metadata.configurator describes the chosen material: sizes, allowed quantities, options (attributes) with their values and default value, graphic services, production days. These are the inputs for price_configuration. For another material pass its id, or selected [{name: 'Materiale', label}] with a label from options: a label that matches no material returns an error listing the valid ones. metadata.help, when present, has up to 3 short FAQ about the product and a link to its knowledge base section: mention them only if they answer the user's question.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- changedInput schema / properties / catalog / properties / id / description
```
Previous value: -"id di prodotto o di materiale."New value: +"Product or material id."
```
First observedOct 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive profile, and the description adds real behavior beyond them: an invalid label returns an error listing valid labels, configurator exposes default values and production days, and help contains at most three FAQs plus a knowledge-base link. No contradiction with readOnlyHint/destructiveHint.

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?

Four sentences, front-loaded with what the tool returns, then the material-selection mechanics, then help guidance. The configurator enumeration sentence is dense but each clause (sizes, quantities, options, graphic services, production days) carries signal. No 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?

There is no output schema, and the description compensates by describing the return sections (UCP fields, configurator contents, help contents) rather than just the call. Only minor gaps remain: the 'UCP fields' are left opaque, and the meta parameter is unaddressed, but an agent can call and interpret the result confidently.

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 effectively 0%, so the description carries most of the load; it explains catalog.id (product or material id) and the selected shape and label semantics well, including the max-five/list-of-options behavior. It says nothing about the meta.ucp-agent.profile parameter, leaving one branch of a nested schema 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?

The description states a concrete retrieval (product details keyed by product or material id) and names the payload sections returned (UCP fields, metadata.configurator, metadata.help), so the agent knows what it gets. It does not explicitly contrast with lookup_catalog or search_catalog, so sibling differentiation is only implicit.

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?

It clearly explains the two ways to target a material (its id, or selected with a label from options) and states that the returned configurator data are the inputs for price_configuration, giving a clear 'use this before pricing' flow. It also gives guidance on metadata.help ('mention them only if they answer the user's question'). It stops short of stating when to prefer this over the sibling search/lookup tools.

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?