Skip to main content
Glama

www.cerano.pl catalog

Search Catalog

search_catalog
Read-onlyIdempotent

Search this shop's product catalog (UCP catalog.search). Dimensions such as '80x80' work in the query. Returns products with price in minor units, availability status, URL and key parameters (metadata.parameters). filters.compatible_with keeps only products that fit a given product. Paginate with pagination.cursor.

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
metaNo
catalogYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), and the description adds genuinely useful behavior: return shape (price in minor units, availability status, URL, metadata.parameters), cursor-based pagination, and the fact that dimension strings are valid query text. It stops short of noting rate limits or that unsupported filters are silently ignored with a message, which the schema covers instead.

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?

Front-loaded with the core purpose, then packed with concrete operational facts in short sentences; almost nothing is wasted. The telegraphic style ('Dimensions such as 80x80 work in the query') is dense but readable, with only minor redundancy around price/minor-units phrasing.

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?

Given an output schema exists, the description needn't document return values, yet it still summarizes the useful ones. It covers query syntax, the key filter, and pagination, leaving only the ignored UCP passthrough fields unmentioned — a minor gap for a search tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With reported schema description coverage at 0% for the two top-level parameters, the description carries real weight: it explains that dimensions belong in the query string, that filters.compatible_with accepts a product ID or SKU and restricts to fitting products, and that pagination.cursor drives paging. That meaningfully compensates for the coverage gap, though it says nothing about the ignored context/signals/attribution objects.

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 this shop's product catalog') with the underlying UCP operation named, so the agent knows exactly what is being queried. It does not explicitly distinguish itself from siblings like lookup_catalog or get_product, so an agent must infer that this is the free-text/browse path rather than a direct ID lookup.

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 implied through the mention of dimension-style queries ('80x80') and the compatible_with filter, which hints at when to use this over a plain lookup. It never states exclusions or explicitly routes to alternatives such as find_compatible or lookup_catalog, so selection guidance is only partial.

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