Skip to main content
Glama

Search TravelCharika

search_places
Read-onlyIdempotent

Find what TravelCharika has a page for, by name: places, countries, regions, kinds of place ("beaches"), activities ("skiing"), seasons, routes, departure cities, months and holidays. Matches as the site's own search box does: accents ignored, a name a place is also known by ("Bombay"), one letter off ("Marrakesh"), and a month among the words ("bali in may") gives that month's page. Returns each match's kind, name, the id the other tools take, and its page. A place under travel advice is found by its name with the advice beside it (advice), and is in no list. Call it first whenever you have a name rather than an id; nothing matching gets the nearest names instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many matches.
queryYesWhat to look for: a place, country, region, kind of place, activity, city to fly from, or a phrase such as "bali in may" or "beaches december".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"What to look for: a place, country, region, kind of place, city to fly from, or a phrase such as \"bali in may\" or \"beaches december\"."New value: +"What to look for: a place, country, region, kind of place, activity, city to fly from, or a phrase such as \"bali in may\" or \"beaches december\"."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond them: accent-insensitive matching, alias support ('Bombay'), one-letter-off fuzziness ('Marrakesh'), month-phrase parsing ('bali in may'), the returned fields, and the special travel-advice case where a place is found by name but appears in no list. This is rich, non-obvious operational detail.

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?

The description is front-loaded with what it searches, followed by matching rules, return shape, edge cases, and usage guidance in a logical order. It is dense and somewhat run-on in the middle, but nearly every clause carries distinct information; nothing is padding.

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?

With no output schema, the description steps in to specify the return fields (kind, name, id, page). It also covers matching behavior, the travel-advice special case, and the no-match fallback, so an agent has everything needed to invoke and interpret results 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, but the description adds real query semantics: it explains that the query accepts not just names but activities, seasons, cities, and natural-language phrases, and that matching mirrors the site's own search box. It does not discuss the 'limit' parameter, leaving that to 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 (find/search) and resource (places) and enumerates the breadth of what is searchable: places, countries, regions, kinds of place, activities, seasons, routes, departure cities, months, holidays. It clearly distinguishes itself from siblings like country_facts, activities, and where_to_go by positioning itself as the name-based entry point.

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?

Explicitly routes the agent: 'Call it first whenever you have a name rather than an id,' and notes that the returned id is 'the id the other tools take,' implying the sibling tools consume ids. It also states the fallback behavior when nothing matches ('gets the nearest names instead'), so the agent knows how to react to an empty result.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources