glasstopfen.de

Look up products

lookup_catalog

Read-onlyIdempotent

Look up products or variants by id (UCP catalog.lookup): catalog.ids = [..].

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
`meta`	No	UCP request metadata: {"ucp-agent": {"profile": "<platform profile URL>"}, "idempotency-key": "<uuid>"}.
`catalog`	Yes	UCP catalog payload, shape per https://ucp.dev/2026-08-25/schemas/shopping/catalog_lookup.json#/$defs/lookup_request
`country`	No	Destination country, ISO 3166-1 alpha-2 (e.g. AT). Needed for final prices; without it prices are EUR estimates.

Output Schema

Name	Required	Description	Default
`ucp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the UCP spec pointer and the ids payload shape, but says nothing about behavior on unknown ids (error vs. partial results) or response shape — the latter is partly covered by the existing output schema.

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?

A single front-loaded sentence with no filler; the parenthetical gives the most useful payload hint immediately. The internal spec token 'UCP catalog.lookup' is somewhat opaque jargon but compresses real information into few words.

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?

For a tool with a free-form nested catalog object and an external-schema reference, the description does the minimum: one payload key and a spec link. An agent gets no guidance on batching limits, missing-id behavior, or why country matters, though the output schema reduces the need to describe returns.

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 coverage is 100%, so the baseline is 3. The 'catalog.ids = [..]' hint does add real value because the schema's catalog property merely defers to an external URL rather than naming keys; nonetheless the description does not cover meta/idempotency-key or explain how country affects final prices.

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 ('look up products or variants by id'), which implicitly separates it from the query-based search_catalog sibling. It does not name an alternative explicitly, but the 'by id' qualifier makes the lookup-vs-search distinction inferable.

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 the phrase 'by id' — the agent can infer this is the tool to use when it already holds product/variant identifiers. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. search_catalog for keyword discovery), so guidance remains implicit.

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

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