Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Sun times, sunrise sunset: sunrise and sunset times and day length for a place and date

sun
Read-only

Sunrise, sunset, solar noon, civil dawn and dusk (UTC) and day length for any place and date, computed with the standard solar equations; handles polar day and night. No outside service. Use for photography, events and outdoor planning. Example: lat=59.33, lon=18.07. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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 (default today)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, yet the description adds materially: computations are local ('No outside service'), polar day/night edge cases are handled, output times are UTC, and billing is per-call ($0.01 x402 USDC or card key, first 25 free, failed calls free). It also reconciles the non-idempotent hint by explaining repeats are charged, which is exactly the kind of condition an agent needs before retrying.

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?

Front-loads the capability and output fields, then moves to constraints and pricing, with no filler sentences. The pricing/auth tail is slightly dense but each clause (free tier, failed calls free) conveys actionable information.

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?

For a three-parameter compute tool with no output schema, the description covers outputs, timezone, edge cases, and cost model thoroughly. The remaining gap is the accepted format for the optional 'date' string (e.g., ISO 8601), which is unspecified in both schema and description and could cause malformed calls.

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% and each parameter already carries a range or default, so the schema does the heavy lifting. The description adds an illustrative coordinate pair (lat=59.33, lon=18.07) but no date format guidance, so it contributes only marginally beyond structured fields.

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 computed resource — 'Sunrise, sunset, solar noon, civil dawn and dusk (UTC) and day length for any place and date' — with the computational basis (standard solar equations). An agent can distinguish it from siblings like moon, time, and weather without opening the 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?

Gives concrete use contexts ('photography, events and outdoor planning') and an example invocation, which tells the agent when this is the right tool. It does not name an exclusion or point to a sibling alternative (e.g., moon or time), so it stops short of full routing guidance.

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.