roamflat Flat configurator

Price grid

price_grid

Read-onlyIdempotent

Prices for several speed × days combinations of one Flat in one call (up to 8 day values; speeds default to all), e.g. to compare with other providers or to find the best fit. Same server prices as quote_flat.

Input Schema

Name	Required	Description
`days`	Yes	Up to 8 day values, e.g. [3,7,14,30].
`flat`	No	Optional: which Flat of the country, as get_flats numbers them. Omit = the cheapest Flat that allows the speed.
`mbps`	No	Speeds to include (default all: 5, 10, 25, 50).
`bucket`	No	Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language.
`currency`	No	Optional ISO 4217 override for prices.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices.
`networks`	No	Optional: operator names from get_flats that must be included (the cheapest Flat holding all of them is used). Ignored when flat is given.
`destination`	Yes	Country in ANY language or its ISO code, e.g. "Japan", "Japon", "jp". Map a city to its country first. One country per Flat.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 17, 2026
- addedInput schema / properties / days / items / maximum
```
Added value: +30
```
- addedInput schema / properties / days / items / minimum
```
Added value: +1
```
- addedInput schema / properties / days / maxItems
```
Added value: +8
```
- addedInput schema / properties / days / minItems
```
Added value: +1
```
- addedInput schema / properties / mbps / items / enum
```
Added value: +[
+  5,
+  10,
+  25,
+  50
+]
```
- addedInput schema / properties / mbps / maxItems
```
Added value: +4
```
AddedOct 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. The description adds one genuinely new behavioral guarantee — that prices match quote_flat's server prices, useful for cross-tool consistency — but repeats schema-level facts ('up to 8 day values; speeds default to all') and says nothing about rate limits, caching, or the shape of the returned price matrix.

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?

Two compact sentences, front-loaded with the core output and its multi-combination scope, followed by usage examples and a cross-tool consistency note. Every clause contributes; nothing is padding, and the most important constraint (the grid nature and 8-value cap) appears first.

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 an 8-parameter read tool with full schema coverage and clear safety annotations, the description covers purpose, scope limits, usage context, and cross-tool consistency. The one omission is the return shape of the price grid — with no output schema, an agent must infer the matrix structure — but that is a minor gap given how self-evident a price grid is.

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 every parameter is already documented in the schema. The description's parameter mentions (day-value cap, speed defaults) merely duplicate the schema, adding no new meaning about defaults, interaction between flat/networks/bucket, or currency precedence. Baseline 3 applies when the schema carries the parameter burden.

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 names a specific output (prices for several speed × days combinations of one Flat in one call) and a concrete constraint (up to 8 day values, speeds default to all), so the resource is unambiguous. It gestures at its relationship to quote_flat via 'Same server prices as quote_flat', which hints at the single-combination vs grid distinction, but it never explicitly frames quote_flat as the sibling for a single quote, so the differentiation stays implicit.

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 contexts — comparing with other providers or finding the best fit — which tells an agent why it would reach for this tool over a plain price lookup. However, it stops short of explicit when-not guidance (e.g. 'use quote_flat instead when you need a single combination'), so the routing rule against the closest sibling is left to inference.

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 tools Inspect

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

Need Help?