Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find place or room code

ot_find_place
Read-onlyIdempotent

Convert a place name into city/province slugs or a room code into room details for Otaghak room searches.

Instructions

Turn a place name into the city / province slugs that ot_search_rooms needs, or a room code into its room.

Cities come with their listing count (undated). A province listings number is not a search count. Room names are not searchable here: use ot_search_rooms with name. Next: ot_search_rooms, or ot_room for a room hit.

Input Schema

NameRequiredDescriptionDefault
queryYesCity/province name (Persian or slug), e.g. 'رامسر', or a room code, e.g. '2508916'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • changedInput schema / properties / query / description
      Previous value: -"City or province name in Persian or as an English slug, e.g. 'رامسر', 'ramsar', 'مازندران', or a numeric room code, e.g. '2508916'."New value: +"City/province name (Persian or slug), e.g. 'رامسر', or a room code, e.g. '2508916'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"ot_find_placeArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_find_placeDictOutput",
-  "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 openWorld, so the safety profile is covered. The description adds real behavioral context beyond them: cities carry an undated listing count, a province listings number is not a search count, and room names are not queryable here.

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 core purpose and no wasted sentences; the caveats each carry distinct meaning. It is telegraphic and slightly dense, but nothing is redundant.

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?

With no output schema, the description does describe what comes back (city with listing count, province listings, room from a code) and flags the two input modes. Complete enough for a single-param resolver, though return structure could be spelled out a touch more.

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 single query param is fully documented with format and examples, so the baseline is 3. The description adds the dual-mode meaning (place name vs room code) and what each resolves to, going slightly 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 and resource: resolving a place name into city/province slugs, or a room code into its room. It distinguishes itself from siblings by naming ot_search_rooms and ot_room as the tools that consume its output.

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?

Explicit routing is present: 'Room names are not searchable here: use ot_search_rooms with name' gives a clear when-not, and 'Next: ot_search_rooms, or ot_room for a room hit' names the alternatives and the condition selecting each.

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