Fuse rooms

Answer a Fuse question

answer_faq

Read-onlyIdempotent

Answer a question about Fuse from the site's own FAQ and city guides, with the same search /ask runs: booking, documents, fees, deposit, cancellation, contracts, moving in and out, house rules and life in Budapest or Riga. Returns the best matching answers, each with the page that shows it. Read only.

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": {
      "question": "<question>"
    },
    "name": "answer_faq"
  }
}

Input Schema

Name	Required	Description
`city`	No	Prefer this city's answers: budapest or riga.
`limit`	No	Most answers to return, 1 to 5. Default 3.
`question`	Yes	The question, in the student's words.

Output Schema

Name	Required	Description
`answers`	Yes
`faq_url`	Yes	The full FAQ.
`message`	Yes	What to do when nothing matches.
`question`	Yes	The question asked.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.5/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 trailing 'Read only' adds nothing. What the description does contribute is the corpus being searched (the site's own FAQ and city guides) and the shape of the result ('best matching answers, each with the page that shows it'), which is modest added context beyond the annotations.

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 core purpose and corpus are front-loaded in the first clause, followed by a compact topic enumeration that helps routing. The closing 'Read only' duplicates annotations and the run-on topic list could be tightened, but there is no real padding.

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?

With a rich annotation set, an output schema, and full schema description coverage, little else is required. The description supplies the source corpus and result form; it would only be stronger if it said how to choose this tool over the topic-adjacent siblings.

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 the city enum, limit bounds and default, and the question field, so the schema already carries parameter meaning. The description only echoes that Budapest/Riga are the supported cities and adds no format or syntax guidance beyond it, making the baseline 3 appropriate.

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?

States a specific verb (answer a question) and resource (Fuse FAQ and city guides) and enumerates the covered topics. It does not, however, distinguish itself from siblings whose names overlap with listed topics such as booking and fees, so an agent could hesitate between this and get_booking_steps or get_prices_and_availability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the topic list tells an agent roughly which questions belong here, but there are no explicit when-to-use/when-not statements and no named alternatives. The phrase 'with the same search /ask runs' gestures at a shared search behavior without clarifying it.

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?