Skip to main content
Glama

www.cerano.hu catalog

Get Product

get_product
Read-onlyIdempotent

Full product detail by product ID (Shoptet GUID) or variant SKU: description, all parameters (e.g. width, depth, shape, series), downloadable documents, availability, rating and the product URL.

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
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 closed-world, so the safety profile is covered and the bar is lower. The description adds payload scope ('full product detail', including documents, availability and rating), which is genuinely useful context, but it says nothing about behavior for unknown IDs, partial matches on variant SKU, or response size.

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?

One front-loaded sentence that puts the identifier options before the payload list, with no filler. The trailing enumeration of returned fields is slightly long and partly duplicates what the output schema already provides, keeping it short of a 5.

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?

For a read-only, idempotent single-record lookup with an output schema and full annotations, the definition covers what the agent needs: the identifier forms and the content returned. Remaining gaps (not-found behavior, variant-vs-parent resolution) are modest rather than disqualifying.

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?

The description mirrors the schema's identifier semantics (Shoptet GUID or variant SKU) without adding format or resolution rules, and it does not touch the nested context/signals/attribution objects at all. With reported schema description coverage at 0%, some meaning is supplied for the critical required parameter, but most of the parameter surface remains unexplained, so this is a minimum-viable score.

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 ('Full product detail by product ID ... or variant SKU') and enumerates the payload (description, parameters, documents, availability, rating, URL), so the agent knows exactly what it retrieves. It does not, however, contrast itself with search_catalog, lookup_catalog or find_compatible, so sibling differentiation is left implicit.

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?

Guidance is only implied: the accepted identifier (Shoptet GUID or variant SKU) signals that this is the exact-lookup path, while search_catalog/lookup_catalog presumably cover broader discovery. There is no explicit 'use this when / not when' statement or named alternative, so a mis-selection between lookup and search remains possible.

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