Fuse rooms

Fuse prices and availability

get_prices_and_availability

Read-onlyIdempotent

Get what a Fuse room costs and when rooms are free: for each room type in Budapest and Riga, the lowest and highest monthly price from the live listing and whether a room is free now or from which date, plus what the price includes, the one time membership fee, the deposit rule and the contract lengths. Give move_in to see which room types have a room free by then. Use search_rooms for single rooms. Read only: it never books, holds, pays, uploads or signs; the booking link is the room's page on fusestays.com, where the student books.

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": {
      "city": "<city>"
    },
    "name": "get_prices_and_availability"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	budapest, riga, or both.
`move_in`	No	Optional move in date as yyyy-mm-dd, or yyyy-mm for any start that month: says per room type whether a room is free by then.
`room_type`	No	Only this room type.

Output Schema

Name	Required	Description
`cities`	Yes
`move_in`	Yes	The move in day asked about (yyyy-mm-dd).
`included`	Yes
`prices_note`	Yes	How the prices work.
`pricing_url`	Yes	The prices page.
`data_read_at`	Yes	When this answer was built (ISO time), not when the listing was read: a city in saved_cities comes from the last good read, up to a day old.
`saved_cities`	Yes	Cities whose rooms, or some of their details, come from the last good read, up to a day old, because the live listing did not fully answer just now: whether a room is free, or a detail, may have changed.
`failed_cities`	Yes	Cities whose room list could not be read just now: they may well have rooms. Try again in a few minutes.
`contract_months`	Yes
`membership_fee_eur`	Yes	Paid once to hold the room.
`contract_start_days`	Yes
`membership_fee_note`	Yes	When it is paid and whether it is refunded.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description reinforces this with an unusually explicit negative scope: 'it never books, holds, pays, uploads or signs.' It goes further by explaining that the booking link is the room's page on fusestays.com and that the student completes the booking there, which is behavior no annotation conveys.

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 definition is front-loaded with the purpose and output contents, followed by short imperative routing sentences, with zero filler. The first sentence is very long and packs many clauses (prices, availability, inclusions, fee, deposit, contracts), which slightly hurts scannability but every element is substantive.

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 a rich output schema, the description covers what the agent needs: data returned, city and per-room-type scoping, the move_in date effect, the sibling alternative, and an explicit safety boundary. Nothing required to select or call the tool correctly is 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%, including enum values and the move_in pattern, so the schema already carries parameter meaning. The description adds only partial context — city scope and the effect of move_in — and largely restates what the schema's own descriptions say about availability by date. Baseline 3 is appropriate.

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 combination ('Get what a Fuse room costs and when rooms are free') and then precisely enumerates the returned data: per room type, min/max monthly price from live listings, free-now status or earliest free date, inclusions, membership fee, deposit rule and contract lengths. It also names the city scope (Budapest and Riga) so the agent can distinguish it immediately from a generic room lookup.

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 a concrete routing rule — 'Use search_rooms for single rooms' — and explains when to supply the optional move_in parameter ('Give move_in to see which room types have a room free by then'). What it lacks is any explicit exclusion for the other siblings (get_room_details, get_booking_steps) or a 'when not to use' statement, so it stops short of a full routing map.

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

All Fuse rooms 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?