TravelType

Search points of interest

search_pois

Read-only

Free-text POI search with prefix/tag/fuzzy ranking plus popularity and geo boosts. Provide q (free text, min 2 chars) and/or city (slug); with both, the search is scoped to that city. Optionally narrow with tags (a POI must carry all of them). At least one of q or city is required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Free-text query (min 2 chars).
`city`	No	Restrict to a city slug.
`lang`	No	Language for human-readable name/description fields. EN is canonical.	en
`tags`	No	Tag slugs; a POI must carry all of them.
`limit`	No	Maximum number of POIs to return (1-50).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pois`	Yes
`count`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJun 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral details about ranking algorithm, parameter requirements (min 2 chars for q, at least one of q or city), and scoping behavior, complementing the annotations without contradiction.

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 sentences, no wasted words. First sentence states purpose and capabilities, second explains parameter requirements. Front-loaded with the main action.

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?

Given output schema exists, description doesn't need to explain return values. It covers essential behavior: free-text search with boosts, scoping, tag filtering, and parameter requirements. Minor omission of pagination details but acceptable for a search tool.

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 adds context about how parameters interact (e.g., scoping to city when both q and city provided) and the ranking behavior, which goes beyond the raw schema 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?

The description clearly states 'Free-text POI search' with specific verb and resource, and lists capabilities like prefix/tag/fuzzy ranking and geo boosts, distinguishing it from sibling tools such as find_similar_pois or get_poi_details.

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 provides clear context on when to use this tool (free-text search with optional city and tags) but does not explicitly mention when not to use it or compare to alternatives.

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

All TravelType tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: find similar POIs, get city/country/POI details, list cities/countries, and search POIs. No overlap.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with underscore_case (e.g., find_similar_pois, get_city, list_cities).

Tool Count5/5

Seven tools is well-scoped for a travel POI server, covering essential operations without being excessive or insufficient.

Completeness4/5

Core CRUD-like operations are covered (list, get, search, find similar). Minor gaps like listing all POIs for a city without free text are mitigated by search_pois with city parameter.

Resources

Need Help?