Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Host profile

ot_host
Read-onlyIdempotent

Check a host's response time, acceptance rate, member since date, active rooms, starting prices, and newest guest reviews by host_id or room_id to judge reliability or explore their other listings.

Instructions

Check a host: response time, response and acceptance rates, member since, active rooms (undated starting prices) and the newest guest reviews across all their rooms.

Pass host_id, or room_id to find the room's host. Use to judge whether a host is reliable or to see their other places.

Input Schema

NameRequiredDescriptionDefault
host_idNoHost id, e.g. 1626813.
room_idNoOr a room id, to find its host.
full_textNoReturn long texts in full instead of clipped.
rooms_limitNoHost's rooms to list.
reviews_limitNoNewest reviews across the host's rooms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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 / host_id / description
      Previous value: -"Host (user) id, e.g. 1626813."New value: +"Host id, e.g. 1626813."
    • removedInput schema / properties / host_id / title
      Removed value: -"Host Id"
    • changedInput schema / properties / reviews_limit / default
      Previous value: -5New value: +3
    • removedInput schema / properties / reviews_limit / title
      Removed value: -"Reviews Limit"
    • changedInput schema / properties / room_id / description
      Previous value: -"Or a room id to look up its host, e.g. 2512254."New value: +"Or a room id, to find its host."
    • removedInput schema / properties / room_id / title
      Removed value: -"Room Id"
    • changedInput schema / properties / rooms_limit / default
      Previous value: -10New value: +6
    • removedInput schema / properties / rooms_limit / title
      Removed value: -"Rooms Limit"
    • removedInput schema / title
      Removed value: -"ot_hostArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_hostDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive semantics, so the burden is lighter. The description nonetheless adds real behavioral context beyond them: prices are 'undated starting prices,' reviews are the 'newest across all their rooms,' and long text is clipped unless requested. Auth/rate-limit behavior is not discussed, keeping it out of 5 territory.

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 tight sentences: the return payload is front-loaded, then the invocation modes and intended use. No filler, no repetition of the title.

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 characterize the return, and it does so explicitly by listing the profile fields. Combined with the input-mode guidance and the clipping caveat, an agent has everything needed to call it correctly.

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 the schema already documents all five parameters. The description clarifies the host_id/room_id input-mode choice, but adds nothing for full_text, rooms_limit or reviews_limit. Baseline 3 is appropriate.

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 ('Check') and resource ('a host') and enumerates exactly what the profile contains: response time, response/acceptance rates, member since, active rooms, newest reviews. An agent can distinguish this from ot_room or ot_reviews without opening a schema.

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?

Explicitly tells the agent how to invoke it ('Pass host_id, or room_id to find the room's host') and names the intent ('judge whether a host is reliable or to see their other places'). It does not, however, explicitly name a sibling alternative such as ot_reviews for pure review retrieval, so it falls just short of a 5.

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