Skip to main content
Glama

www.livero.cz catalog

Find Compatible

find_compatible
Read-onlyIdempotent

Products that fit a given product: shower trays for a shower enclosure, walk-in screen or niche door, and enclosures, screens or doors for a shower tray. compatibility.status: fits (fits as is), fits_after_cut (a cuttable tray is cut to size), floor_only (no tray fits: the screen goes on the tiled floor only), unknown (data missing, never present it as a match), not_applicable (we do not track compatibility for this product type). Each returned product has metadata.compatibility with the evaluated variant sku, verdict, reason code and a message in the shop language. Results are capped per role and total is the full count; to narrow a long list use search_catalog with a query and filters.compatible_with.

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": {
      "id": "<id>"
    },
    "name": "find_compatible"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct ID (Shoptet GUID) or variant SKU.
roleNoReturn only this product type.
limitNoProducts per role (the server caps it).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish a safe read (readOnlyHint true, idempotent, closed-world), so the bar is lower, and the description still adds real context: the full verdict vocabulary including the warning to never present "unknown" as a match, the per-role result cap with "total" as the full count, and the shape of the returned compatibility metadata. It does not explain whether the limit cap is fixed or configurable by the server, but that is a minor omission against otherwise strong disclosure.

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?

The purpose is front-loaded, and each subsequent sentence carries real information: the role pairings, the verdict enum semantics, the return metadata, and the routing alternative. It is dense and slightly run-on, with a compressed parenthetical enum list, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with an output schema, the description covers the gaps that matter: what the verdict codes mean, the special handling of "unknown", how limits combine with total, and where to go for filtered search. Nothing an agent needs in order to interpret or correctly invoke the tool appears to be missing.

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%, so the schema already documents id (GUID or variant SKU), role (product type filter), and limit (products per role, server-capped). The description reinforces the per-role cap and total count but adds no syntax, defaults, or edge-case meaning beyond what the schema states; a baseline 3 reflects that the schema is doing the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-and-resource statement ("Products that fit a given product") and immediately grounds it in the actual domain pairings: shower trays for an enclosure/screen/door, and enclosures/screens/doors for a tray. That directional detail lets an agent tell what comes back without opening the schema, and it names search_catalog as the narrowing path, so it is clearly distinguishable from at least one sibling.

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?

It gives one explicit routing rule: to narrow a long list, use search_catalog with a query and filters.compatible_with. But it never states when to call find_compatible versus the similarly named check_compatibility sibling, or when the tool should not be used at all; those conditions are left for the agent to infer.

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