Skip to main content
Glama

www.cerano.ro catalog

Check Compatibility

check_compatibility
Read-onlyIdempotent

Check a set of 2 to 20 products (e.g. a shower enclosure and a tray) before recommending them together. Returns a verdict for every pair (a, b = product IDs, a_sku, b_sku = the evaluated variants): fits, fits_after_cut (the cuttable tray is cut to size), incompatible, unknown (data missing, not a match) or not_applicable (we do not track compatibility for that pair), with a reason code and a message in the shop language.

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": {
      "ids": "<ids>"
    },
    "name": "check_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes2 to 20 product IDs (Shoptet GUID) or variant SKUs.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so safety is covered. The description adds genuinely non-obvious behavior: the exact verdict vocabulary, the meaning of fits_after_cut (the cuttable tray is cut to size), the unknown-vs-not_applicable distinction, and that every pair returns a reason code and a shop-language message.

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?

Two sentences, front-loaded with the action and batch size, then a compact enumeration of verdicts. The verdict list is long but each term earns its place since the agent must interpret the response; no filler or repeated framing.

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?

With an output schema present, the description needn't spell out the return shape, yet it still explains the verdict semantics, reason codes and message language, which is enough to call and interpret the tool. One residual ambiguity: the description caps input at 20 while the schema sets maxItems to 100, a discrepancy the agent has no guidance to resolve.

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 100% and the single `ids` parameter is already documented as 2-20 Shoptet GUIDs or variant SKUs, so the description mostly restates it. It does add useful pair-level semantics by defining a, b as product IDs and a_sku, b_sku as the evaluated variants, which clarifies what the returned identifiers refer to.

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?

The definition pairs a specific verb and resource ("check a set of 2 to 20 products") with the concrete scenario of validating a batch before recommending items together, which is clearly a pairwise compatibility check rather than a lookup. It never names the sibling find_compatible, so an agent must infer the boundary from the batch-of-pairs framing alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"before recommending them together" supplies a real usage context, telling the agent this is a pre-recommendation validation gate. There are no explicit exclusions or an instruction about when to prefer find_compatible or lookup_catalog instead, so the guidance stops short of full routing.

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