Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Room reviews and rating

ot_reviews
Read-onlyIdempotent

Get a room's overall rating, star histogram, category scores, recommendation percentage, and written guest reviews with host replies to judge quality before booking.

Instructions

Get a room's rating (0-5), star histogram, six category scores, percent of guests who recommend it, and written reviews, newest first (with host replies).

rating is null and reviews empty when the room has no ratings yet (new rooms). Use after ot_room or ot_search_rooms to judge quality; ot_host has reviews across all of a host's rooms.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page.
limitNoReviews per page.
room_idYesRoom id (code), e.g. 2512254.
full_textNoReturn long texts in full instead of clipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.2.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return long texts in full instead of clipped.",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / default
      Previous value: -10New value: +5
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based page number."New value: +"Zero-based page."
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / room_id / title
      Removed value: -"Room Id"
    • removedInput schema / title
      Removed value: -"ot_reviewsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_reviewsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: ordering (newest first), inclusion of host replies, and the edge case where rating is null and reviews are empty for new rooms — a detail not in annotations or schema.

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 the returned payload and followed by the caveat and routing guidance. No filler; every clause carries information.

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?

There is no output schema, so the description must convey the return shape — and it does, listing rating, histogram, category scores, recommendation percent, and reviews. Combined with the edge-case note, an agent has everything needed to call and interpret this tool.

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 page, limit, room_id, and full_text are all documented in the schema itself (including clipping behavior tied to full_text). The description adds no parameter-level syntax or format detail, so the baseline of 3 applies.

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 — retrieves a room's rating, star histogram, category scores, recommendation percent, and written reviews — and implicitly distinguishes itself from ot_host, which covers reviews across all of a host's rooms.

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?

Gives explicit timing ('Use after ot_room or ot_search_rooms to judge quality') and names the alternative sibling (ot_host) with the condition that selects it. An agent can route correctly without opening either schema.

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

Deploy Server

Other Tools