ScorpTech x402 Tools

Sun Times

sun_times

Read-onlyIdempotent

Sunrise, sunset, solar noon, day length, civil / nautical / astronomical twilight, golden hour and blue hour for any place and date (NOAA solar calculator equations, about a minute of accuracy), with polar day / night handling, observer elevation correction and local times in any IANA zone. Optionally the sun's azimuth and elevation (refraction-corrected) at a given moment. Offline. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sun-times

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

Input Schema

Name	Required	Description	Default
`at`	No	ISO 8601 moment for sun position (azimuth / elevation), or "now"
`tz`	No	IANA time zone for the output	UTC
`lat`	Yes
`lon`	Yes
`date`	No	Local date YYYY-MM-DD (default today in tz)
`elevation`	No	Observer height above the horizon in metres (earlier sunrise / later sunset)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, and the description adds meaningful behavioral context: NOAA equations, about one minute of accuracy, polar day/night handling, elevation correction, offline operation, and x402 pricing.

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?

It front-loads the returned quantities and keeps pricing/endpoint details brief, though the first sentence is dense and slightly run-on.

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 tool with no output schema, it enumerates the returned fields and key edge cases such as polar day/night, elevation correction, and timezone handling, but it does not specify the response shape.

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 coverage is 67% and already documents tz, date, elevation, and at; the description reinforces IANA-zone output and optional sun position at a moment but adds little syntax or format detail beyond the schema. 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?

The description names the exact solar quantities returned and the scope ('for any place and date'), making the tool's purpose immediately clear and distinguishable from weather or moon-related siblings.

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 'for any place and date' and the optional azimuth/elevation moment, but there is no explicit when-to-use or when-not guidance and no comparison to related tools such as moon_phase or weather_global.

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

All ScorpTech x402 Tools tools Inspect

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

Need Help?