Skip to main content
Glama

Sunrise, sunset, solar noon and day length for a coordinate

sun
Read-only

Sunrise, sunset, solar noon and day length for a coordinate and date (default today), with the moonrise, moonset and phase. Times are ISO 8601 with the offset MET Norway gives (+00:00 is UTC). Attribution: data from MET Norway (CC BY 4.0). Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "sun"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, -90 to 90
lonYesLongitude, -180 to 180
dateNoDate, YYYY-MM-DD (default today)

Output Schema

NameRequiredDescriptionDefault
latNo
lonNo
sunNo
dateNo
moonNo
timesNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 description's real value is the operational detail it adds: ISO 8601 times with the MET Norway offset, data attribution/license, and — importantly — a paid invocation model ($0.002 per successful call via x402, failures not charged). That payment requirement materially affects whether an agent should call it, which the annotations never reveal. It stops short of mentioning rate limits, caching, or how polar day/night edge cases are reported.

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?

Three tight sentences: purpose first, then output/timezone semantics, then attribution and cost. Nothing is buried and nothing is filler; the only minor redundancy is repeating the 'default today' already in the schema.

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 an output schema present, the description doesn't need to enumerate return fields, and it correctly focuses on timezone interpretation, licensing, and billing. It is nearly complete for a simple 3-parameter read tool; the remaining gap is edge-case behavior (polar latitudes with no sunrise/sunset) and what a failed/uncharged call looks like.

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 coverage is 100%, so lat/lon ranges and the YYYY-MM-DD format are already fully documented. The description only restates the date default ('default today'), which duplicates the schema, and adds no interpretation of coordinates, timezone-of-input expectations, or format requirements beyond what the schema says.

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 names the exact quantities returned (sunrise, sunset, solar noon, day length) plus the resource (coordinate and date), and mentions the added moonrise/moonset/phase. That is far more specific than a generic 'solar times' label, though it doesn't distinguish itself from any sibling because no sibling overlaps this domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'for a coordinate and date (default today)' tells the agent what inputs to supply, but there is no explicit when-to-use guidance, no exclusions, and no pointer to a related tool for a different time granularity or a different location format.

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