India Hotels MCP

Resolve a place in India

resolve_place

Read-onlyIdempotent

Converts place names or codes into coordinates, or coordinates into nearby transport points. Finds railway stations, airports, bus stations, and landmarks for trip planning.

Instructions

Turns a name or code into coordinates, or coordinates into nearby transport points. With query: matches railway station codes and names, airport IATA codes and names, bus stations, and landmarks or localities via OpenStreetMap geocoding, returning ranked matches with kind, code and lat/lng. With lat/lng: returns the nearest railway stations (within 10 km), airports with IATA codes (within 60 km) and bus stations (within 5 km), with straight-line distances. Does not search hotels.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude, for nearby transport points.
`lng`	No	Longitude, for nearby transport points.
`kind`	No	Only return this kind of place.
`limit`	No	Maximum matches for a query.
`query`	No	Name or code, e.g. 'Howrah', 'BLR', 'Hawa Mahal'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	Yes
`nearby`	Yes
`matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds genuinely useful behavior beyond that: the per-kind search radii (10/60/5 km), straight-line distance semantics, ranked matches, and returned fields.

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?

Two dense sentences, front-loaded with the dual-mode purpose followed by detail. Nearly every clause earns its place, though the enumerated radii and field lists make it slightly heavy for a single paragraph.

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?

An output schema exists, so return values needn't be explained, yet the description still names returned fields. Combined with explicit mode scoping, radii, and exclusions, an agent has everything needed to invoke it correctly.

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 baseline is 3. The description goes further by explaining the mutually exclusive query-vs-coordinates modes and their distinct semantics, which is meaning beyond the per-field schema text.

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 precise bidirectional verb+resource: name/code to coordinates, or coordinates to nearby transport. It enumerates the exact place kinds (stations, airports, bus stations, landmarks/localities) and explicitly distinguishes itself from siblings with 'Does not search hotels.'

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?

The description clearly scopes the two operating modes ('With query' vs 'With lat/lng'), which is real when-to-use guidance. It lacks explicit routing to named alternatives beyond the negative 'Does not search hotels', so it stops short of full alternative selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server