Skip to main content
Glama
Flightmussy

Sunshine Atlas MCP server

Find sunny destinations

find_sunny_destinations

Find sunny destinations ranked by Sunshine Score for any month. Filter by continent, country, minimum temperature, population, or swimmable sea temperature.

Instructions

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, or swimmable sea (≥21°C). Every result has a citable sunshineatlas.com URL.

Input Schema

TableJSON 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.
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
Behavior4/5

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

No annotations; description covers data source (climate normals), scoring (0-100), and citable URL. No destructive behavior mentioned, transparent.

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, main purpose front-loaded, no fluff. Efficient.

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?

No output schema but mentions citable URL and sorts. Could specify return format more, but sufficient for a search tool with good parameter descriptions.

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?

100% schema coverage, baseline 3. Description adds value: month format, 'where' explains traveler definition for Europe, min_population default 0 includes small islands, etc.

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?

Description clearly states it finds sunny destinations for a given month, sorted by Sunshine Score, with filters. Distinct from siblings (compare, get 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?

Implied usage: when user asks for sunny destinations in a month. No explicit when-not or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flightmussy/sunshine-atlas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server