Skip to main content
Glama

Solar path for a day

get_solar_path
Read-onlyIdempotent

The sun's azimuth and altitude through one UTC day, sampled every interval: a list of timestamped positions. Use it for shading studies, PV siting and panel-angle planning; for a single instant use get_solar_position. date defaults to today and interval to 15m. Requires an API key on a paid Solar plan.

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": "get_solar_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees.
dateNoUTC day as YYYY-MM-DD. Defaults to today.
intervalNoSampling step. Defaults to 15m.
elevationNoMetres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zero. For irradiance it is height above sea level. Supply it when known: from a height the sun rises measurably earlier than the sea-level answer. Omit only if it is genuinely unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / elevation / description
      Previous value: -"Metres above sea level. Supply it when known: at altitude the sun rises measurably earlier than the sea-level answer. Omit only if the elevation is genuinely unknown."New value: +"Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zero. For irradiance it is height above sea level. Supply it when known: from a height the sun rises measurably earlier than the sea-level answer. Omit only if it is genuinely unknown."
  2. Changed4 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Day as YYYY-MM-DD."New value: +"UTC day as YYYY-MM-DD. Defaults to today."
    • changedInput schema / properties / interval / description
      Previous value: -"Sampling step, e.g. 5m, 15m, 1h."New value: +"Sampling step. Defaults to 15m."
    • addedInput schema / properties / interval / enum
      Added value: +[
      +  "1m",
      +  "5m",
      +  "15m",
      +  "1h",
      +  "1d"
      +]
    • removedInput schema / properties / tz
      Removed value: -{
      -  "description": "IANA timezone for output timestamps, e.g. Europe/Dublin.",
      -  "type": "string"
      -}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the paid Solar plan API-key requirement, the UTC-day scope, the sampling behavior, and the general return shape. It stops short of documenting units, precision, or failure/quota behavior, which keeps it from a 5.

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?

Front-loads what the tool returns, then use cases, the alternative tool, defaults, and the auth requirement. Each clause carries distinct information with no filler.

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 five-parameter tool with no output schema, the description adequately covers purpose, return shape, defaults, and access requirements. It could be stronger by stating the units of the returned azimuth/altitude and the timestamp format, but nothing critical to invoking the tool is missing.

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 description coverage is 100%, and the schema itself already states that date defaults to today and interval defaults to 15m. The description repeats those defaults but adds no meaning about lat, lon, elevation, or accepted interval values beyond what the schema provides, so the baseline 3 is appropriate.

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 resource and scope: the sun's azimuth and altitude across one UTC day, sampled at a chosen interval, returned as timestamped positions. It explicitly distinguishes itself from get_solar_position for single-instant queries, so an agent can route correctly 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 Guidelines5/5

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

Gives concrete use cases (shading studies, PV siting, panel-angle planning) and names the alternative tool for a single instant. That is an explicit when-to-use rule plus a sibling disambiguation.

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.