Skip to main content
Glama

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.

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_daily_light_integral"
  }
}

Input 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. 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. 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"
      -}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds real substance beyond the readOnly/idempotent annotations: the clear-sky assumption and how to interpret it, the fact that results are per UTC day, and the auth requirement (API key on a paid Solar plan). It stops short of describing response shape or any limits on range length.

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?

Four tight sentences, front-loaded with what the value is, then usage, then parameter behavior, then prerequisite — nothing redundant.

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 read-only computed metric with no output schema, the units, assumption, and date semantics cover what an agent needs; only the structure of the returned per-day series and any range-length constraint are left implicit.

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?

With 100% schema coverage the baseline is 3, and the description earns a bump by stating the pairing rule (from and to together, or neither for today) and the 'today' default, which the schema does not spell out.

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?

Defines the exact quantity, its units (mol/m²/day), and the integration basis (PAR from sunrise to sunset), which lets an agent immediately separate it from the solar-position and tide siblings 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 concrete use case (planning crop growth or supplemental greenhouse lighting) and the interpretive caveat that cloudless-sky output is a ceiling, but never names an alternative tool or states when another endpoint would be preferred over this one.

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.