Skip to main content
Glama

BRAINIAC Geo & Environment Lookups

Compute sunrise sunset and solar position

geo-environment_sun-times-position
Read-onlyIdempotent

Compute sunrise, solar noon, sunset, day length and solar elevation/azimuth with NOAA Solar Calculator equations. Price $0.01 USDC. POST /api/v1/geo-environment/sun-times-position. An unpaid call returns the x402 payment terms and does not run.

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>"
    },
    "name": "geo-environment_sun-times-position"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNodate, string. Optional.
instantNoinstant, string, length 10 to 40. Optional.
latitudeYeslatitude, number, from -90 to 90. Required.
timeZoneNotimeZone, string, length 1 to 80. Required.UTC
longitudeYeslongitude, number, from -180 to 180. Required.

Output Schema

NameRequiredDescriptionDefault
dateNodate. String.
polarNopolar. Null.
methodNomethod. String.
sunsetNosunset. String.
sourcesNosources. Array.
sunriseNosunrise. String.
accuracyNoaccuracy. String.
positionNoposition. Object.
solarNoonNosolarNoon. String.
limitationsNolimitations. Array.
dayLengthMinutesNodayLengthMinutes. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely non-annotated behavior: a $0.01 USDC price, the exact POST endpoint, and that an unpaid call returns x402 payment terms instead of executing. That monetization behavior is the most important thing an agent needs and is not derivable from annotations.

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?

Three short sentences, front-loaded with the capability, then commercial terms, then endpoint. Nothing is redundant; the endpoint and price are operational facts rather than padding.

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?

An output schema exists, so return values need no explanation, and annotations cover safety semantics. The description fills the remaining non-obvious gap — that this is a paid x402 endpoint that will not run unpaid — making it complete enough to invoke 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 documents latitude/longitude ranges and the optional date/instant fields. The description adds no parameter-level meaning beyond that, which matches the baseline for high-coverage schemas.

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 verb (Compute) with the exact resource set: sunrise, solar noon, sunset, day length, solar elevation/azimuth, and names the underlying NOAA Solar Calculator equations. It does not distinguish itself from the sibling geo-environment tools, but their functions are unrelated, so the gap is minor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the computed quantities rather than stated: an agent infers this is for solar ephemeris at a coordinate. There is no explicit when-to-use or when-not-to-use guidance relative to alternatives, though the payment flow tells the agent what happens on an unpaid call.

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