Skip to main content
Glama

www.cerano.sk catalog

Lookup Catalog

lookup_catalog
Read-onlyIdempotent

Look up products by product ID (Shoptet GUID) or variant SKU (UCP catalog.lookup). Unknown IDs are reported in messages as not_found.

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

NameRequiredDescriptionDefault
metaNo
catalogYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: unknown IDs surface in messages as not_found, implying partial-success semantics. It does not say whether missing IDs are errors, whether ordering is preserved, or what the response shape looks like.

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 identifier types and the not_found behavior are stated early. Parenthetical UCP/catalog.lookup tags add length without much operator value, keeping it short of ideal.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. Given a simple two-parameter batch lookup with nested optional UCP fields, the definition covers purpose, identifier kinds and failure signaling; only mixed-result behavior and the 20-ID cap are left to the schema.

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 reported as 0%, so the description carries more of the burden, but it largely restates the ids parameter's own semantics (product IDs / variant SKUs) without adding format, deduplication, or ordering rules. The nested meta/context/signals/attribution parameters are not addressed at all, though the schema itself marks them ignored.

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") and scopes the lookup to two identifier kinds (Shoptet GUID or variant SKU). It does not explicitly distinguish itself from sibling tools like get_product or search_catalog, so an agent must infer the boundary.

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: needing an ID or SKU is the unstated precondition for this tool versus a search. There is no explicit when-not guidance, no mention of the sibling alternatives, and no statement about batching limits or what to do when not_found appears in messages.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources