Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Popular destinations and collections

ot_destinations
Read-onlyIdempotent

Find destinations when no city is chosen: browse popular cities and themed villa collections, get collection codes for ot_search_rooms, or list cities a collection covers.

Instructions

Popular cities and collections (themed landing pages: discounted, jungle villas, villas with pool, ...).

Use when the user has no destination yet, or to find collection codes for ot_search_rooms collection. With collection, also lists the cities that collection covers (city slugs).

Input Schema

NameRequiredDescriptionDefault
collectionNoCollection code to list its cities, e.g. 'beach'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • changedInput schema / properties / collection / anyOf
      Previous value: -[
-  {
-    "description": "Slug (letters, digits, -).",
-    "pattern": "^[A-Za-z][A-Za-z0-9-]{1,60}$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^[A-Za-z][A-Za-z0-9-]{1,60}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / collection / description
      Previous value: -"Collection code to list its cities, e.g. 'beach', 'jungle', 'villa-north-iran', 'lastsecond'."New value: +"Collection code to list its cities, e.g. 'beach'."
    • removedInput schema / properties / collection / title
      Removed value: -"Collection"
    • removedInput schema / title
      Removed value: -"ot_destinationsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_destinationsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds a genuine behavioral nuance beyond the schema: when `collection` is supplied, the response also lists the cities that collection covers (as city slugs), which changes what the caller should expect back.

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 short sentences plus a clause; the core purpose is front-loaded and every sentence carries actionable information (examples, trigger condition, sibling linkage). No filler.

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?

There is no output schema, so the description carries the burden of hinting at returns; it does this by noting the city-slug listing behavior. For a zero-required-param read tool this is nearly complete, though it could say more about the shape of the default (no-argument) response.

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?

Schema coverage is 100% and the schema already documents `collection` with an example ('beach'), so baseline is 3. The description goes further by explaining the semantic effect of passing the parameter (it switches the tool to listing covered cities and yields slugs), adding meaning beyond the schema text.

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 resource ('popular cities and collections') and clarifies what collections are with concrete examples ('themed landing pages: discounted, jungle villas, villas with pool'). It does not explicitly differentiate itself from sibling discovery tools like ot_deals, ot_travel_guide, or ot_find_place, so it stops short of a 5.

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?

Gives a clear triggering condition ('use when the user has no destination yet') and names the downstream consumer ('to find collection codes for ot_search_rooms `collection`'). It lacks an explicit when-not clause (e.g., what to use once a destination is known), which keeps it from 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