compare_roomsCompare selected public room listings side by side for price, distance, type, availability, features, and trust signals.
| Name | Required | Description | Default |
|---|---|---|---|
| room_ids | Yes | ||
| campus_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| rooms | Yes | ||
| comparison | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "comparison": {
+ "additionalProperties": false,
+ "properties": {
+ "closest_room_id": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "lowest_price_room_id": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "most_reviewed_landlord_room_id": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "lowest_price_room_id",
+ "closest_room_id",
+ "most_reviewed_landlord_room_id"
+ ],
+ "type": "object"
+ },
+ "rooms": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "available_from": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "campus_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cover_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "deposit_amount": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "distance_km": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "feature_summary": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "label": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ },
+ "unit": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "value": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "number"
+ },
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "value_label": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "code",
+ "label",
+ "type",
+ "unit",
+ "value",
+ "value_label"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "id": {
+ "type": "integer"
+ },
+ "landlord_avatar_url": {
+ "type": "string"
+ },
+ "landlord_is_verified": {
+ "type": "boolean"
+ },
+ "landlord_name": {
+ "type": "string"
+ },
+ "landlord_rating_average": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "landlord_rating_count": {
+ "type": "integer"
+ },
+ "landlord_role": {
+ "type": "string"
+ },
+ "location_label": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "location_name": {
+ "type": "string"
+ },
+ "min_stay_months": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "occupancy_status": {
+ "type": "string"
+ },
+ "price_currency": {
+ "type": "string"
+ },
+ "price_monthly": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "public_url": {
+ "type": "string"
+ },
+ "room_city": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "room_country_code": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "room_type": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title": {
+ "type": "string"
+ },
+ "university_city": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "university_country_code": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "university_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "zone_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "price_monthly",
+ "price_currency",
+ "room_type",
+ "location_name",
+ "public_url",
+ "feature_summary"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "rooms",
+ "comparison"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no repeating. The description adds one genuine behavioral nugget — only 'public' listings are comparable — but says nothing about the 2–8 room bounds, error behavior for private/invalid IDs, or result ordering.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, verb-first, no filler, and the enumerated dimensions give the reader immediate value. Nothing to trim and nothing relevant repeated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and the listed dimensions roughly preview it. However, for a tool with two undocumented parameters and hard cardinality limits, the description omits constraints an agent must know to call it successfully.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for two parameters, so the description must carry the burden and largely fails: room_ids is only obliquely implied by 'selected ... listings' and campus_id is never mentioned at all. Neither the minItems=2/maxItems=8 limits nor the campus scoping semantics are surfaced.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (compare) and resource (public room listings) and enumerates the compared dimensions. The 'side by side' framing implicitly separates it from single-room tools like get_room_details, but it never names an alternative, so sibling differentiation is inferred rather than explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no stated prerequisites, and no mention of the practical constraints (min 2 / max 8 rooms, or how campus_id affects the comparison). The agent is left to infer the intended invocation context from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.