ScorpTech x402 API

Moon Phase

moon_phase

Read-onlyIdempotent

Moon phase for any moment: phase name and emoji, illuminated fraction, phase angle, age in days since new moon, waxing / waning, Earth-Moon distance and apparent size, the next new moon / first quarter / full moon / last quarter (to a few minutes), and moonrise / moonset for a location and local date (topocentric, parallax and refraction aware). Meeus lunar theory, offline. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/moon-phase

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "moon_phase"
  }
}

Input Schema

Name	Required	Description	Default
`at`	No	ISO 8601 moment (default now); a bare date means local noon in tz
`tz`	No	IANA zone for output times	UTC
`lat`	No	Latitude for moonrise / moonset
`lon`	No	Longitude for moonrise / moonset

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond annotations: offline Meeus lunar theory, topocentric parallax/refraction-aware calculations, event precision, and payment terms ($0.001 USDC per successful x402/Solana call).

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?

The definition is front-loaded with the core capability and packs many useful output fields into one dense sentence. It is somewhat run-on, but the price and alternative HTTPS endpoint are relevant and no major sentence is wasted.

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?

With no output schema, the description carries the return-value burden and lists the key outputs in detail. Combined with 100% parameter schema coverage and annotations covering safety, it gives an agent enough to understand what the call returns and how it behaves.

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 at, tz, lat, and lon. The description reinforces that location and local date affect moonrise/moonset, but it does not add new syntax or format meaning beyond the schema.

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?

The description clearly states the resource and scope: moon phase for any moment, with a detailed list of astronomical outputs. It is specific enough to distinguish this from most numeric/date siblings, but it does not explicitly contrast with related tools such as sun_times or date_calc.

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 moment' and by the note that moonrise/moonset require a location, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The context is understandable but left to inference.

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

All ScorpTech x402 API 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?