TravelType
Server Details
Search and explore a global travel points-of-interest catalog (cities, countries, POIs).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 7 of 7 tools scored.
Each tool has a clearly distinct purpose: find similar POIs, get city/country/POI details, list cities/countries, and search POIs. No overlap.
All tools follow a consistent verb_noun pattern with underscore_case (e.g., find_similar_pois, get_city, list_cities).
Seven tools is well-scoped for a travel POI server, covering essential operations without being excessive or insufficient.
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.
Available Tools
7 toolsfind_similar_poisFind similar POIsRead-onlyInspect
Find the nearest POIs to the given one by tag-cosine similarity (shared distinctive tags) — 'more like this'. Empty when the POI has only generic tags.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | POI UUID or slug. | |
| lang | No | Language for human-readable name/description fields. EN is canonical. | en |
| limit | No | Maximum number of similar POIs to return (1-30). |
Output Schema
| Name | Required | Description |
|---|---|---|
| pois | Yes | |
| count | Yes |
get_cityGet city detailsRead-onlyInspect
Get one city by slug, including POI count, top distinctive tags, top categories, and a sample of its top POIs.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for human-readable name/description fields. EN is canonical. | en |
| slug | Yes | City slug, e.g. 'berlin'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| lat | Yes | |
| lng | Yes | |
| name | Yes | |
| slug | Yes | |
| name_en | No | |
| top_tags | No | |
| poi_count | Yes | |
| sample_pois | No | |
| country_iso2 | Yes | |
| wikidata_qid | No | |
| top_categories | No |
get_countryGet country detailsRead-onlyInspect
Get one country by ISO 3166-1 alpha-2 code, including its active cities (top 100 by POI count).
| Name | Required | Description | Default |
|---|---|---|---|
| iso2 | Yes | ISO 3166-1 alpha-2 code, e.g. 'DE'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| iso2 | Yes | |
| cities | No | |
| name_de | Yes | |
| name_en | Yes | |
| poi_count | Yes | |
| city_count | Yes | |
| name_local | No | |
| wikidata_qid | No |
get_poi_detailsGet POI detailsRead-onlyInspect
Get one POI by UUID or slug, with full enrichment: coordinates, approved tags, categories, Wikidata/OSM/Google identifiers, and hero image.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | POI UUID or slug. | |
| lang | No | Language for human-readable name/description fields. EN is canonical. | en |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| lat | Yes | |
| lng | Yes | |
| url | Yes | |
| name | Yes | |
| slug | Yes | |
| tags | Yes | |
| osm_id | No | |
| city_slug | No | |
| image_url | No | |
| categories | No | |
| description | No | |
| country_iso2 | No | |
| image_source | No | |
| wikidata_qid | No | |
| google_place_id | No |
list_citiesList citiesRead-onlyInspect
List active cities ordered by POI count, with coordinates and Wikidata QID. Paginate with limit/offset; filter by ISO 3166-1 alpha-2 country code.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of cities to return (1-100). | |
| offset | No | Number of cities to skip, for pagination. | |
| country | No | ISO 3166-1 alpha-2 country code filter, e.g. 'DE'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| limit | Yes | |
| total | Yes | |
| cities | Yes | |
| offset | Yes |
list_countriesList countriesRead-onlyInspect
List every country that has at least one active city, with city and POI counts.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| countries | Yes |
search_poisSearch points of interestRead-onlyInspect
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.
| 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
| Name | Required | Description |
|---|---|---|
| pois | Yes | |
| count | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!