Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Help: rules and FAQ

ot_help
Read-onlyIdempotent

Read Otaghak's help center to find FAQ answers, booking and cancellation policies, refunds, wallet, check-in, host rules, or quality policy. Search by Persian query or browse questions.

Instructions

Read Otaghak's help center: the FAQ, or the guest terms (booking and cancellation rules, the five cancellation policies, refunds, wallet, check-in rules), host rules or quality policy.

Without query you get every FAQ question (short answers) or the section titles of a page with a preview; with query the matching FAQ items or page paragraphs. A room's own cancellation policy is in ot_room.

Input Schema

NameRequiredDescriptionDefault
queryNoPersian words to look for, e.g. 'لغو', 'کیف پول'.
topicNofaq, terms (booking, cancellation policies, refunds, wallet, stay rules), host_rules, quality_policy.faq

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for, Persian works best, e.g. 'لغو' (cancellation) or 'کیف پول' (wallet)."New value: +"Persian words to look for, e.g. 'لغو', 'کیف پول'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / properties / topic / description
      Previous value: -"faq: the help-center FAQ; terms: guest terms of use (booking, cancellation policies, refunds, wallet, stay rules); host_rules; quality_policy."New value: +"faq, terms (booking, cancellation policies, refunds, wallet, stay rules), host_rules, quality_policy."
    • removedInput schema / properties / topic / title
      Removed value: -"Topic"
    • removedInput schema / title
      Removed value: -"ot_helpArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_helpDictOutput",
-  "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, non-destructive, and open-world, so the safety profile is covered. The description adds the genuinely useful behavioral detail that no-query returns all questions/section titles with previews while query returns matching items or paragraphs — a real difference in return shape the annotations do not convey.

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 paragraphs, zero filler. The domain list is front-loaded, the query behavior is explained next, and the sibling redirect closes with no wasted words.

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?

For a two-parameter read-only content tool with no output schema and full schema coverage, the description is complete: it covers scope, both parameter modes, the enum topics, and the one ambiguous case (room-level policy) by naming the correct alternative.

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%, so the baseline is 3, but the description goes further: it explains the query parameter's effect on result granularity (whole list vs. matching paragraphs) and names the topic domains in prose, reinforcing the enum. It adds semantic value beyond the schema's terse field descriptions.

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 (Read) and resource (Otaghak's help center), and enumerates the content domains (FAQ, guest terms, host rules, quality policy). It also explicitly distinguishes itself from ot_room for room-specific cancellation policies, which no other sibling covers.

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?

Explains the query/no-query branching clearly, telling the agent when to search versus when to list whole sections, and routes room-specific policy lookups to ot_room. It does not, however, say when to choose this over ot_travel_guide or ot_reviews, which are plausible adjacent content siblings.

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