Skip to main content
Glama

thirdtrail

by io.github.thirdtrail
OverviewDiscussionsAdmin

Daily light integral

get_daily_light_integral
Read-onlyIdempotent

Clear-sky Daily Light Integral in mol/m²/day for each day in a range: photosynthetically active radiation integrated from sunrise to sunset. Use it to plan crop growth or supplemental greenhouse lighting; it assumes cloudless skies, so treat it as the ceiling for the site. Pass from and to together for a range of UTC days, or neither for today. Requires an API key on a paid Solar plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLast UTC day, YYYY-MM-DD. Requires from.
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees.
fromNoFirst UTC day, YYYY-MM-DD. Requires to.
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. Changed3 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"Range start, YYYY-MM-DD."New value: +"First UTC day, YYYY-MM-DD. Requires to."
    • changedInput schema / properties / to / description
      Previous value: -"Range end, YYYY-MM-DD."New value: +"Last UTC day, YYYY-MM-DD. Requires from."
    • removedInput schema / properties / tz
      Removed value: -{
-  "description": "IANA timezone for output timestamps, e.g. Europe/Dublin.",
-  "type": "string"
-}
  2. Added

TDQS

A4.1/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 non-open-world. The description adds value beyond them: the clear-sky modeling assumption, the ceiling interpretation, and the auth prerequisite ('Requires an API key on a paid Solar plan'). It does not describe output shape or rate limits, keeping it out of 5 territory.

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: quantity/unit first, then purpose and caveat, then parameter behavior and auth. No filler, well front-loaded.

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 single-metric read tool with no output schema, the description conveys the unit, per-day granularity, range semantics, assumptions, and auth requirement. Return-format detail is absent but the metric's shape is adequately implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds default behavior the schema does not state: passing from/to together for a range, or neither for today. That is real semantic gain beyond the individual 'Requires to'/'Requires from' notes.

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?

States a specific quantity with its unit ('Clear-sky Daily Light Integral in mol/m²/day') and scope ('for each day in a range'), which is distinctive against siblings like get_solar_position or get_prayer_times. It does not explicitly name a sibling, but the resource itself is unique enough that confusion is unlikely.

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 clear intent ('plan crop growth or supplemental greenhouse lighting') and an important interpretation caveat (cloudless skies, treat as the ceiling). It omits any when-not or explicit alternative tool, but the context is unambiguous for its niche.

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