MAQAMI Travel

get_data_places

Read-onlyIdempotent

Find cities, airports, and areas, returning Place IDs to set hotel search boundaries and power location autocomplete.

Instructions

Overview

Search for places, locations, and areas using Google Places API. Returns a list of matching places that can be used to search for hotels within specific boundaries.

Pricing: $0.01 per request

When to Use

Location autocomplete - Build location search with autocomplete suggestions
Place selection - Let users select cities, airports, or areas
Hotel search boundaries - Get Place IDs to restrict hotel searches to specific regions
Location discovery - Find places by name or description

What You Get

Place list - Multiple matching places with details
Place IDs - Unique identifiers for use in hotel searches
Location information - Names, addresses, and location types
Formatted addresses - Human-readable addresses for display

Key Features

Multiple types - Search for cities, airports, hotels, or other place types
Type filtering - Specify place types (e.g., 'locality,airport,hotel')
Smart defaults - Automatically excludes less relevant types unless specified
Relevance ordering - Results sorted by relevance using Google's ranking

Quick Start

Provide a textQuery (e.g., "Manhattan") and optionally specify type to filter results. Returns matching places with Place IDs you can use in hotel searches.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Restricts the results to places matching the specified type(s). You can specify a single type (e.g., 'hotel') or multiple types as a comma-separated list (e.g., 'locality,airport,hotel'). Common types include: 'locality' (cities), 'airport', 'hotel', 'lodging', 'establishment', 'point_of_interest'. When multiple types are provided, results from all types are merged and ordered by relevance.
`clientIP`	No	The IP address of the client making the request.
`language`	No	The language code, indicating in which language the results should be returned. e.g. 'en'
`sessionId`	No	Optional Google Places billing session ID. When provided, this autocomplete call is bundled into a session settled by a subsequent place details call, reducing billing costs. Can also be passed via the X-Places-Session-Id header (header takes priority). If omitted, the server manages a fallback session automatically.
`textQuery`	Yes	Search query. e.g. 'Manhattan'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.8/5.0

Behavior4/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 genuinely new behavioral context beyond the annotations: per-request pricing ($0.01), relevance ordering via Google's ranking, and smart defaults that exclude less relevant place types unless specified.

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

Conciseness3/5

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

Headers make it scannable and front-loaded, but the five-section layout is padded — 'What You Get' and 'Key Features' partly restate each other, and the Quick Start repeats the Overview. It is serviceable but not tight; several bullets could be dropped without losing information.

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 usefully compensates by describing return contents (place list, Place IDs, addresses, location types). It covers purpose, pricing, usage, and returns, leaving only minor gaps such as result limits/pagination behavior.

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 description coverage is 100% and the schema already documents textQuery, type, language, clientIP and sessionId in detail, so the baseline is 3. The description only echoes the textQuery example and the comma-separated type syntax; its one real addition is the 'smart defaults' note about type exclusion, which is marginal beyond the schema.

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?

The description names a specific verb and resource ('Search for places, locations, and areas using Google Places API') and states the return type (a list of matching places). It implicitly distinguishes itself from get_data_places_placeid (detail lookup by ID) by emphasizing list search and Place ID retrieval, though it never names that sibling explicitly.

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 'When to Use' section gives four concrete scenarios (autocomplete, place selection, hotel-search boundaries, location discovery), which is clear contextual guidance. It stops short of 5 because no alternatives or exclusions are named — it never says when to prefer get_data_cities or get_data_places_placeid instead.

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

Deploy Server