Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Destination travel guide

ot_travel_guide
Read-onlyIdempotent

Retrieve a destination's travel guide with FAQs, related city themes, and matching blog articles to understand what a place is like and what to do there.

Instructions

Get the site's travel guide for a destination: guide text, the destination's FAQ (best season, sights, prices), related search pages (city themes such as beach, cottage, apartment with listing counts) and matching blog articles (restaurants, sights, souvenirs).

Use when the user asks what a place is like or what to do there. City theme slugs from related_pages go to ot_search_rooms city_tag.

Input Schema

NameRequiredDescriptionDefault
kindNoWhat `place` is.city
placeYesCity, province or collection slug, e.g. 'ramsar', 'beach'.
full_textNoReturn long texts in full instead of clipped.
max_charsNoMax characters of the guide text.
blog_queryNoBlog search words, e.g. 'رستوران رامسر'. Default: place name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.2.0
    • changedInput schema / properties / blog_query / description
      Previous value: -"Blog search words, e.g. 'رستوران رامسر'. Default: the place's Persian name."New value: +"Blog search words, e.g. 'رستوران رامسر'. Default: place name."
    • removedInput schema / properties / blog_query / title
      Removed value: -"Blog Query"
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return long texts in full instead of clipped.",
+  "type": "boolean"
+}
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • changedInput schema / properties / max_chars / default
      Previous value: -3000New value: +2000
    • removedInput schema / properties / max_chars / title
      Removed value: -"Max Chars"
    • changedInput schema / properties / place / description
      Previous value: -"City, province or collection slug, e.g. 'ramsar', 'mazandaran', 'beach'."New value: +"City, province or collection slug, e.g. 'ramsar', 'beach'."
    • removedInput schema / properties / place / title
      Removed value: -"Place"
    • removedInput schema / title
      Removed value: -"ot_travel_guideArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_travel_guideDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds useful composition context (what data areas the guide aggregates) but doesn't disclose clipping behavior or defaults, which full_text and max_chars imply but don't explain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and the enumeration of return content, then a clear when-to-use block. The parenthetical examples (beach, cottage, apartment) and blog subtopics add length but are informative rather than 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?

A read-only aggregation tool with a fully documented schema; the description covers purpose, trigger, contents, and one cross-tool chaining case. Return format details are appropriately left to the schema/annotations, though the clipping behavior when full_text is false could be spelled out.

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 coverage is 100%, so every parameter is already documented, including what place/kind mean and the max_chars clipping behavior via full_text. The description adds the cross-tool hint that related_pages slugs map to ot_search_rooms `city_tag`, but no additional parameter syntax or format detail beyond the schema.

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 (get) and resource (travel guide for a destination) and enumerates the return contents (guide text, FAQ, related search pages, blog articles). This distinguishes it from siblings like ot_destinations or ot_find_place, which locate destinations rather than describe them.

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 gives the trigger condition ('when the user asks what a place is like or what to do there') and a concrete chaining instruction routing theme slugs to ot_search_rooms `city_tag`. No exclusion guidance for other guide-like siblings, but the when-to-use is clear.

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