Skip to main content
Glama
Sign In
meteo-swiss-mcp

meteo-swiss-mcp

by cuolm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

astronomy_sun

Read-only

Get sunrise, sunset, and civil twilight start/end times for a Swiss location and date to know when it is light outdoors.

Instructions

        Get when the Sun rises and sets at a place on a day, and when civil twilight begins and ends.

        Use this for "when does the sun rise tomorrow" or "until when is it light tonight". Civil
        twilight is the light before sunrise and after sunset; outside it, artificial light is
        normally needed outdoors. The times are for a level horizon, so in a valley the Sun
        appears later behind the mountains.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            date (str): The day, e.g. "2026-09-23".

        Returns:
            dict: The place, the date, the begin of civil twilight, sunrise, sunset and the end of
                civil twilight.

        Examples:
            astronomy_sun("Zürich", "2026-09-23")

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": {
      "location": "<location>",
      "date": "<date>"
    },
    "name": "astronomy_sun"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
nearNoOnly when several places share the name: a village next to the place the user means. For "the Blausee near Bettmeralp" use location "Blausee" and near "Bettmeralp". Leave it out otherwise.
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the definition of civil twilight, the note that times assume a level horizon and shift in a valley, and the geographic restriction to places in Switzerland.

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 key purpose and usage triggers are front-loaded and the prose is readable. The trailing Args/Returns/Examples block largely restates the schema and signature, which is mild redundancy rather than noise.

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?

With no output schema, the Returns section usefully enumerates the returned fields (place, date, twilight begin, sunrise, sunset, twilight end). Combined with the horizon caveat and geographic scope, an agent has enough to call it correctly; only pagination/error behavior is unaddressed, which is irrelevant here.

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 only 33%, with location and date carrying no schema descriptions, so the description must compensate. It does: location is specified as a Swiss place name with an example, and date is given as a YYYY-MM-DD string with an example. The 'near' parameter is left to the schema, which documents it well, so nothing important is lost.

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?

The opening sentence names a specific resource and verb: sunrise, sunset, and civil twilight bounds for a place on a day. It is trivially distinguishable from siblings such as astronomy_moon and the forecast_* tools because it is explicitly solar and time-of-day oriented.

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?

It gives concrete trigger phrasings ("when does the sun rise tomorrow", "until when is it light tonight") that map user intent to the tool. It does not explicitly exclude alternatives like astronomy_moon or forecast_sunshine, but the solar scope makes the boundary obvious.

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

Deploy Server

Other Tools