Skip to main content
Glama
Sign In

glasstopfen.de

by de.glasstopfen
OverviewDiscussionsAdmin

Get product

get_product
Read-onlyIdempotent

Get one product with its variants (UCP get_product): catalog.id.

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

NameRequiredDescriptionDefault
metaNoUCP request metadata: {"ucp-agent": {"profile": "<platform profile URL>"}, "idempotency-key": "<uuid>"}.
catalogYesUCP catalog payload, shape per https://ucp.dev/2026-08-25/schemas/shopping/catalog_lookup.json#/$defs/get_product_request
countryNoDestination country, ISO 3166-1 alpha-2 (e.g. AT). Needed for final prices; without it prices are EUR estimates.

Output Schema

NameRequiredDescriptionDefault
ucpYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety behavior is covered. The description adds that variants are returned and that this follows the UCP get_product shape, but does not discuss what happens when the product is missing or how the catalog payload affects results.

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 description is a single terse sentence with no wasted wording and the core verb/resource is front-loaded. It is close to the title, making the parenthetical the only genuinely additive element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, the nested UCP catalog payload is complex and the description gives no orientation to what the required catalog object should contain beyond an external schema URL, leaving a moderate 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 100%, so the schema already documents meta, catalog, and country including the note that country affects final prices versus EUR estimates. The description only hints at catalog.id and adds no further parameter meaning 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 states a specific verb and resource ('Get one product') and adds that variants are included, which distinguishes it from list-style sibling tools like search_catalog or lookup_catalog. The parenthetical 'catalog.id' signals single-product lookup, though it is terse and slightly cryptic.

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 only implied by 'Get one product' and the reference to a catalog.id; there is no explicit when-to-use or when-not-to-use guidance versus lookup_catalog, search_catalog, or related retrieval tools. An agent can infer the single-product lookup case but is not told about alternatives.

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

All glasstopfen.de toolsInspect
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