Fuse rooms

Fuse room details

get_room_details

Read-onlyIdempotent

Get the facts about one Fuse room from the live listing: monthly price for each contract length, any length offer, deposit, membership fee, what the price includes, when it is free, address, size and nearby universities, with the room's page URL. Give the room id or the page URL that search_rooms returned. 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": {
      "room": "<room>"
    },
    "name": "get_room_details"
  }
}

Input Schema

Name	Required	Description	Default
`room`	Yes	Room id (like la-ri-01-01-04) or the room's page URL.
`contract_months`	No	Contract length to quote price_eur for. Default 12.

Output Schema

Name	Required	Description
`room`	Yes	The room, or null when no room has that id.
`terms`	Yes	Fees, deposit and contract rules for the room's city.
`booking`	Yes	Who can book.
`how_to_book`	Yes	How the student books it.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description earns credit for adding beyond them: the data comes from the 'live listing', and the tool 'never books, holds, pays, uploads or signs', with booking handled on fusestays.com. It stops short of describing caching or data freshness in more detail.

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?

Purpose is front-loaded in the first clause and the three sentences stay on task: what it returns, how to supply the room, what it will not do. The long field enumeration partially duplicates the output schema and could be trimmed without losing selection value.

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 two-parameter read tool with a full output schema and complete annotations, nothing essential is missing: input sourcing, scope, and the safety/booking boundary are all covered. The listing of returned facts is redundant with the output schema but harmless.

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 defines both parameters, including the contract_months enum and default. The description only lightly reinforces this by saying the monthly price is quoted per contract length; it adds no syntax, default, or edge-case guidance beyond the schema.

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?

States a specific verb and resource ('Get the facts about one Fuse room from the live listing') and enumerates exactly what facts: price per contract length, deposit, membership fee, address, size, nearby universities. That enumeration separates it cleanly from search_rooms, which only surfaces ids and URLs.

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?

Tells the agent where the input comes from ('Give the room id or the page URL that search_rooms returned'), which implies the natural search-then-detail flow. It also redirects the booking action elsewhere ('the booking link is the room's page on fusestays.com'), but it never explicitly contrasts with siblings like get_prices_and_availability.

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?