Skip to main content
Glama

roamflat Flat configurator

by com.roamflat
OverviewDiscussionsAdmin

Shop facts

get_shop_facts
Read-onlyIdempotent

What roamflat is and how the Flat works, in the shop's own words: speeds, networks, when the days start, delivery, payment, refund policy, adding days, My Flat, e-mails, app, devices, support. Use for any question that is not a price.

Input Schema

NameRequiredDescriptionDefault
bucketNoOptional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language.
languageNoISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / bucket
      Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language.",
+  "type": "string"
+}
    • addedInput schema / properties / language
      Added value: +{
+  "description": "ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices.",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is covered. The description adds useful framing that the content is 'in the shop's own words' (verbatim/authoritative vendor copy), but says nothing about return shape or coverage limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence stating what the resource is, followed by a compact topic enumeration and one routing clause. No filler; every clause tells the agent what content is reachable.

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 no-argument, read-only knowledge tool with no output schema, the topic enumeration is enough for an agent to know it can answer policy/spec questions from here. Return formatting is not covered, but the annotations and coverage topics make the definition largely self-sufficient.

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 coverage is 100% and both bucket and language are fully documented in the schema, so the description does not need to repeat them. It adds no extra meaning about how these affect the returned facts, so the baseline 3 applies.

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 enumerates the exact knowledge domain it retrieves (speeds, networks, day start, delivery, payment, refund policy, app, devices, support) and explicitly distinguishes itself from price-related siblings via 'Use for any question that is not a price.' The retrieval verb itself is only implicit, but the resource and scope are unambiguous.

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?

Gives a clear routing rule: use it for any non-price question, which implicitly excludes price queries handled by price_grid/quote_flat/start_checkout. It does not name those siblings explicitly, so the agent must infer which price tool to fall back to.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All roamflat Flat configurator toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources