Skip to main content
Glama
Sign In

glasstopfen.de

by de.glasstopfen
OverviewDiscussionsAdmin

Search catalog

search_catalog
Read-onlyIdempotent

Search the product catalog (UCP catalog.search). Put the destination country in catalog.context.address_country for final prices in local currency. Optional vehicle filter: catalog.filters.vehicle = {make, model, year}.

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

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_search.json#/$defs/search_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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: prices are only final when a destination country is supplied, otherwise they are EUR estimates, and an optional vehicle filter narrows results. It could go further on result volume or pagination, but the pricing caveat is the consequential behavior here.

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 tight sentences with the core purpose front-loaded and no filler; the protocol tag and the two operational hints each earn their place. Slight deduction because the country handling is stated twice in conflicting locations rather than once unambiguously.

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 and annotations cover the safety profile, so return values need not be explained, and the schema links the full UCP request shape. What is missing is routing guidance against the many catalog-adjacent siblings and a resolution of the duplicated country field, which matter for a nested-payload search tool.

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 baseline is 3. The description adds value by prescribing where the country belongs (catalog.context.address_country) and the shape of the vehicle filter, but that prescription sits in tension with the schema's separate top-level `country` property, leaving the agent unsure whether to set one, the other, or both.

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 ("Search the product catalog") and pins the protocol operation (UCP catalog.search), so the agent knows exactly what is being invoked. It does not distinguish this from plausible siblings such as lookup_catalog, get_product, or find_set_for_vehicle, so sibling disambiguation is left to the agent.

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?

Gives task-level instructions for correct invocation (populate catalog.context.address_country for local-currency prices; optional vehicle filter via catalog.filters.vehicle). It never states when to prefer this over lookup_catalog, get_product, or find_set_for_vehicle, so the choice among catalog tools is only implied.

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