Skip to main content
Glama

WritersLogic business agents

solar-position

Sun position, sunrise and sunset for a place and instant (NOAA equations) — Computes sun elevation, azimuth, declination, equation of time, sunrise, solar noon and sunset (UTC) for a latitude/longitude and up to 100 caller-supplied instants using the NOAA Global Monitoring Laboratory solar calculator equations (Meeus). Polar day and polar night return sunrise and sunset as null with a reason, not an error. Reads no clock: every instant comes from the caller. Does not mode

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "asOf": "<asOf>"
    },
    "name": "solar-position"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYesISO 8601 instant with Z or numeric offset; the call never reads the clock.
claimNoOptional claim about the asOf instant to check; tolerances default to 0.5 deg and 2 minutes.
instantsNoFurther instants, same place.
latitudeYesDegrees north, -90 to 90.
longitudeYesDegrees east, -180 to 180.
utcOffsetMinutesNoOffset from UTC used to define the local calendar day for sunrise/sunset (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that polar day/night yield null sunrise/sunset with a reason rather than an error, that no clock is read, and that an optional claim is checked against tolerances. The trailing fragment 'Does not mode…' signals an undisclosed limitation, which is the one real gap.

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?

Outputs and the constraint that the caller supplies instants are front-loaded, and the sentence is dense with no filler. The truncated closing clause 'Does not mode' is a defect that leaves a fragment in place of an actual caveat.

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?

There is no output schema, and the description compensates by enumerating the returned quantities and the polar-day/night null contract in UTC. A six-parameter tool with a nested claim object is adequately covered, though the aborted final sentence suggests an unstated limitation.

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 the baseline is 3 — every parameter including the nested claim object and tolerance defaults is already documented in the schema. The description only reinforces the batch size (up to 100 instants) and adds nothing about utcOffsetMinutes, which is arguably the least obvious parameter.

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 verb and resource — computes sun elevation, azimuth, declination, equation of time, sunrise, solar noon and sunset for a lat/lon plus caller-supplied instants — and grounds the method (NOAA/Meeus). An agent can tell exactly what this tool returns 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 a clear condition of use: the caller must supply every instant ('Reads no clock'), and batching up to 100 instants at one place is explicitly supported, which implies the preferred single-call pattern. It does not name any alternative or exclusion, though no sibling appears to overlap this domain.

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