Skip to main content
Glama

www.cerano.hr catalog

Find By Space

find_by_space
Read-onlyIdempotent

Shower enclosure finder by measured space. Give placement (niche, corner, threewall, walkin) and width_cm (plus depth_cm for corner and threewall). Returns enclosure options per type and shape with category links and sample products. Each product carries metadata.compatibility in the same shape as find_compatible, limited to shower trays that fit both the enclosure and the measured space: status fits = a tray fits as is; fits_after_cut = no exact tray, only a cuttable one shortened to compatibility.cut_to; floor_only = no tray, the enclosure goes on a tiled floor; unknown = data missing, do not claim a fit. A niche tray is never wider than the measured niche. Relay the returned message. An option may have no sample products: use its category links. exact=false means no enclosure has this size and the nearest available size is returned instead: tell the customer.

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": {
      "request": "<request>"
    },
    "name": "find_by_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: returned compatibility statuses, what each status means, how exact=false changes the result, and what to do when sample products are absent. It also includes customer-facing instructions such as relaying the returned message and informing the customer about nearest-size substitutions.

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 description is front-loaded with purpose and required inputs, then moves into return semantics and status definitions. It is dense but mostly earns its length, though some instructions are packed together and could be more cleanly structured.

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 tool with nested request parameters and compatibility metadata, the description covers the critical behavioral details an agent needs: input structure, exact-match fallback, compatibility status meanings, niche constraints, and handling missing sample products. The output schema can carry return shape, while the description supplies the interpretation rules.

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 names the required fields and the conditional need for depth_cm for corner and threewall placements. However, it does not add much meaning beyond the nested schema, which already documents the placement enum and per-placement interpretation of width_cm.

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 description clearly states a specific verb and resource: a shower-enclosure finder based on measured space. It is distinguishable from generic catalog search, but it does not explicitly differentiate itself from siblings such as find_compatible or check_compatibility.

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?

It gives clear usage context by instructing the agent to supply placement, width_cm, and depth_cm where relevant. It does not provide explicit when-not-to-use guidance or name a specific sibling alternative for overlapping use cases.

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