Skip to main content
Glama

Find sunny destinations

find_sunny_destinations

Ranked answer to "where is it sunny (and warm) in ?" — destinations sorted by that month's 0–100 Sunshine Score (long-term climate normals). Filter by continent or country, minimum daytime temperature, population, swimmable sea (≥21°C), or a ceiling on the midday UV index. Every result carries that month's temperatures, rain, midday UV (WHO scale) and sea temperature, plus a citable sunshineatlas.com URL.

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": "find_sunny_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results (default 10, max 50)
monthYesMonth name ("November", "nov") or number 1–12
whereNoOptional continent ("Europe", "Asia", "North America", …) or country (name or ISO-2 code) to search within. "Europe" uses the traveler definition and includes the Canary Islands.
max_midday_uvNoOnly places whose typical midday UV index that month is at or below this (WHO scale: ≤2 low, ≤5 moderate, ≤7 high). For sun-sensitive travellers — "sunny but not fierce".
min_day_high_cNoOnly places at least this warm by day that month, °C
min_populationNoOnly places with at least this population (default 0 = include small islands and outposts)
require_swimmable_seaNoOnly coastal places with sea ≥21°C that month

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / month / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / month / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / max_midday_uv
      Added value: +{
      +  "description": "Only places whose typical midday UV index that month is at or below this (WHO scale: ≤2 low, ≤5 moderate, ≤7 high). For sun-sensitive travellers — \"sunny but not fierce\".",
      +  "type": "number"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the ranking basis, data source (long-term climate normals), filtering behavior, and the per-result fields including temperatures, rain, UV, sea temperature, and a citable URL. It does not mention permissions, rate limits, or error behavior, but those are minor for a read-only ranked search.

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 the core purpose and ranking basis, and it is reasonably efficient despite being dense. The filter list and output-field sentence are useful, though they partly duplicate schema details that are already fully documented.

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?

Although there are no annotations or output schema, the description explains the ranking method, data source, filters, and returned fields including a citable URL, which is enough for correct selection and invocation. Required inputs, defaults, and limits are covered by the schema.

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 seven parameters, making 3 the baseline. The description summarizes the filter concepts but adds no syntax, defaults, or format details beyond what the schema provides; for example, the 'Europe' traveler definition including the Canary Islands appears only in 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 states a specific search/ranking purpose: destinations ranked by a month-specific 0–100 Sunshine Score from long-term climate normals. It clearly distinguishes this as a ranked search tool, but it does not explicitly differentiate itself from siblings compare_destinations or get_destination_climate.

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 use case is clear from the framing 'where is it sunny (and warm) in <month>?' and the available filters. It does not name alternatives or explain when to use compare_destinations or get_destination_climate instead, so it lacks explicit exclusions or sibling routing.

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