VALUE Verdicts

Celestial body state

celestial_state

Read-only

Computes compact, factual ecliptic positions and motion for selected planets, dwarf planets, or supported minor bodies at an Earth coordinate and local civil time. The result is calculated by the configured ephemeris service; it is not a static lookup or an interpretation. Price: $0.01 USDC per call after 25 free calls per day.

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": {
      "dateTime": "<dateTime>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezoneId": "<timezoneId>",
      "bodies": "<bodies>"
    },
    "name": "celestial_state"
  }
}

Input Schema

Name	Required	Description
`bodies`	Yes	One to 20 supported body names.
`_payment`	No	x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used.
`dateTime`	Yes	Local civil time, exactly YYYY-MM-DDTHH:mm.
`latitude`	Yes	Observer latitude from -90 to 90.
`longitude`	Yes	Observer longitude from -180 to 180.
`timezoneId`	Yes	IANA timezone at the observer, e.g. Pacific/Auckland.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description still adds real context: results are computed live by the configured ephemeris service rather than looked up, and there is a cost model ($0.01 USDC per call after 25 free calls/day). This is exactly the kind of behavioral disclosure annotations cannot carry. It does not describe result shape or failure modes (e.g., what happens for unsupported bodies at a given time).

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 sentences ordered purpose → reliability/behavior → cost, with no filler. The pricing detail is placed last where it belongs, and the exclusion ('not a static lookup or an interpretation') is compact and load-bearing.

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 query with full schema documentation and no output schema, the description covers what the tool produces at a high level ('compact, factual ecliptic positions and motion') and flags the paid path. Only the concrete return fields and error behavior are absent, which is a minor gap given the schema already documents the payment flow.

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 100%, so every parameter including _payment is already documented, warranting the baseline of 3. The description only loosely echoes the schema by grouping bodies into planets, dwarf planets, and minor bodies, without adding format constraints like how dateTime and timezoneId interact for local civil time.

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 and resource ('Computes ... ecliptic positions and motion') scoped to selected bodies at an Earth coordinate and local civil time. The clause 'not a static lookup or an interpretation' implicitly separates it from interpretive or table-based siblings, though no sibling is named explicitly.

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 context is implied by the required coordinate/time/bodies framing, and the pricing sentence signals a paid call, but the description never says when to prefer celestial_event_window, celestial_relations, or celestial_earth_projection. The agent must infer the boundary from the tool name alone.

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

All VALUE Verdicts 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?