Fuse rooms

How booking a Fuse room works

get_booking_steps

Read-onlyIdempotent

Explain how a student books a Fuse room in Budapest or Riga: the steps from choosing a room to moving in, as the site runs them now, the documents to upload, the fee, deposit and first rent and when each is paid, who the tenancy agreement is with, and why only the student can book (the booking includes an ID check). Read only: it never books, holds, pays, uploads or signs; the student books on the room's own page.

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_booking_steps"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	City of the room: budapest or riga.

Output Schema

Name	Required	Description
`city`	Yes	City id.
`links`	Yes
`steps`	Yes
`payments`	Yes
`agent_can`	Yes
`documents`	Yes
`team_checks`	Yes	What to tell the student when an AI agent helps with the booking form: the Fuse team may check the booking first.
`documents_note`	Yes	When the documents are uploaded and checked.
`only_the_student`	Yes
`tenancy_agreement_note`	Yes	An exception, when the city has one.
`tenancy_agreement_with`	Yes	The local company the tenancy agreement is with.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false; the description adds concrete meaning beyond them by enumerating the actions it never performs (book, hold, pay, upload, sign) and by noting the content reflects "the site runs them now." It does not discuss freshness of the underlying data or any retrieval limits, which keeps it from a 5.

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?

Front-loaded with the core purpose and the read-only disclaimer placed at the end for emphasis. It is a single long clause-chained sentence, dense but with little wasted wording; splitting the exclusion into its own sentence would improve scanability.

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 one-parameter read-only explanation tool with an output schema and rich safety annotations, the description covers scope, content, and exclusions adequately. Nothing is needed in order to call it correctly; only the sibling disambiguation against pricing and FAQ tools is thin.

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% with a single enum parameter, so the schema fully documents city. The description only restates "Budapest or Riga" with no additional semantics such as case sensitivity or defaulting, so 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?

Specific verb ("Explain") plus a well-bounded resource: the booking steps for a Fuse room in Budapest or Riga, with an enumerated content list (steps, documents, fee/deposit/first rent timing, tenancy agreement, ID-check rationale). The scope largely separates it from search_rooms and get_room_details, though the mention of "the fee, deposit and first rent" overlaps get_prices_and_availability without being disambiguated.

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?

The use case is clear (a student asking how booking works) and the negative guidance is unusually strong: "it never books, holds, pays, uploads or signs; the student books on the room's own page." It stops short of naming alternatives for pricing or general FAQ questions, so routing versus get_prices_and_availability and answer_faq is left implicit.

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?