realtycalendar-web-mcp

List rooms

list_rooms

Read-onlyIdempotent

Retrieve room categories and their rooms, including IDs, capacity, and maximum guests, for a RealtyCalendar hotel. Use it to map room types and guest limits; check availability separately.

Instructions

Room categories (типы номеров) of the user's hotel in RealtyCalendar and the rooms in each, with ids, capacity and max guests. No availability or prices: use check_availability. Other tools take names directly, so this is not needed first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rooms"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`categories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world behavior, and the description adds meaningful scope context: this is a pure discovery/config read with no pricing or availability data, and calling it is optional in a workflow. It stops short of describing result shape or what happens if the hotel has no categories, but the output schema covers return values.

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 sentences, front-loaded with what it returns, then the exclusion and routing guidance. The parenthetical Russian term disambiguates the domain vocabulary without bloat; nothing is wasted.

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 zero-parameter read-only lister with an output schema and full annotation coverage, this description supplies everything an agent needs: what comes back, what it does not cover, which sibling handles the gap, and whether it must be called first.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4; there is nothing for the description to clarify beyond noting the call takes no arguments implicitly. The sentence about fields returned adds context about what the empty schema yields, which is a slight plus.

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 ('Room categories ... of the user's hotel ... and the rooms in each') plus the fields returned (ids, capacity, max guests). It also distinguishes itself from the availability-oriented siblings, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

Explicitly excludes availability and prices and routes to check_availability, and explicitly says it is 'not needed first' because other tools take names directly — a rare, useful anti-pattern warning that prevents an unnecessary call.

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

Deploy Server