Skip to main content
Glama

Where to go

where_to_go
Read-onlyIdempotent

Where is good to go in a month, as the site's list of places answers it: every place open that month, the most visited first (how often travellers look it up; the weather never moves a place up or down), narrowed by the filters given -- a region, a kind of place, what to do (hiking, the sea, snow), the weather in words, quiet only, and from a departure city how far (close by, 3 to 6 hours' flying, long-haul). Each place comes with its month as its card shows it: the site's label (sweet spot, good or ok), the weather word, the typical daytime high, rainy days, busy or quiet, and how far from the city given; with how many places fit, and the same list on the site with its filters set. A place under travel advice is never listed. For one place's twelve months, use best_months.

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": {
      "month": "<month>"
    },
    "name": "where_to_go"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional: a kind of place, by name or id ("Beaches", "mountains", "islands"); several separated by commas for any of them.
limitNoAt most this many places, the most visited first.
monthYesA month: 1 to 12, or its name ("December", "dec").
quietNoOptional: true for quiet places only, leaving out the ones busy that month.
regionNoOptional: a region, by name or id ("Europe", "south-asia"); several separated by commas for any of them.
how_farNoOptional, with from_city: close (a road of up to four hours, or up to three hours' flying), medium (3 to 6 hours' flying) or far (long-haul).
weatherNoOptional, any of them: the weather in words, each a band of the month's average daily high -- hot 30 °C or more, warm from 23, mild from 15, cool from 8, cold below 8.
activityNoOptional, any of them: hiking (a month good for walking all day), sea (the beach and sea good or fair) or snow (a ski place whose lifts run that month).
from_cityNoOne of TravelCharika's departure cities, by its airport code ("DEL", "LON") or its name ("Delhi", "London", "Bombay"). Optional: each place then says how far it is, and how_far can narrow the list by it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: places with travel advice are never listed, and ranking is by traveller lookup frequency with weather explicitly not influencing order.

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?

It is front-loaded with purpose, but delivered as one long dash-and-parenthesis-laden run-on that is hard to parse, and portions (weather band values, distance definitions) repeat the schema verbatim. Every idea is relevant, yet the structure costs readability.

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 compensates by enumerating the returned card fields (label, weather word, daytime high, rainy days, busy/quiet, distance), the match count, and the site link. Combined with the exclusion rule and the sibling pointer, nothing needed to call it correctly is missing.

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%, so the schema already documents all nine parameters, including weather bands and how_far distances. The description largely restates those definitions ("hot 30 °C or more", "3 to 6 hours' flying") rather than adding syntax or defaults beyond the schema; baseline 3 applies.

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 and resource (find places good to go in a given month), the ordering (most visited first), and the filter dimensions in one pass. It explicitly distinguishes itself from best_months, so an agent can tell the two apart without opening either schema.

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?

Clearly routes the agent for the main adjacent use case ("For one place's twelve months, use best_months") and describes when the result set applies (places open that month). It does not differentiate against other plausible siblings such as search_places or activities, so it stops short of full alternative coverage.

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