Skip to main content
Glama

thirdtrail

by io.github.thirdtrail
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
-}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds the return shape, default values, and an important access constraint: an API key on a paid Solar plan is required.

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?

The description is compact and front-loaded: output shape first, then use cases, alternative tool, defaults, and access requirement. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description summarizes the return value as a list of timestamped azimuth/altitude positions. Combined with full parameter schema coverage and annotations covering safety, an agent has enough to invoke it correctly.

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%, so the schema already explains each parameter including bounds, defaults, and elevation rationale. The description reinforces date and interval defaults but adds no parameter syntax or constraints beyond the schema.

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 description states a specific resource and output: the sun's azimuth and altitude through one UTC day, sampled at an interval, as timestamped positions. It also distinguishes the tool from get_solar_position by contrasting daily path versus single instant.

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?

It gives explicit use cases (shading studies, PV siting, panel-angle planning) and directly routes single-instant queries to get_solar_position. The defaults for date and interval further clarify expected usage.

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

All thirdtrail toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources