VALUE Verdicts

Celestial angular relations

celestial_relations

Read-only

Computes the selected bodies, then returns every pairwise angular separation in degrees. Useful for astronomy, historical reconstruction, rendering, research, and event-planning agents. It returns geometry only, with no predictive or interpretive claims. Price: $0.02 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_relations"
  }
}

Input Schema

Name	Required	Description
`bodies`	Yes	Two 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.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds meaningful behavioral context beyond annotations: it returns geometry only with no predictive or interpretive claims, and it discloses pricing after 25 free calls per day.

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 behavior and return value. The domain list and pricing sentence are useful but slightly broad/boilerplate, so it is efficient without being maximally tight.

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?

There is no output schema, but the description explains the return value as pairwise angular separations in degrees. Inputs are fully covered by the schema, and the description adds the geometry-only limitation and pricing model. It is complete enough for correct invocation, though it does not clarify ordering or handling of pairwise results.

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 all parameters are already documented in the schema. The description only implies that 'bodies' are selected and angle output is in degrees; it does not add syntax, constraints, or meaning beyond the structured schema.

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 first sentence states a specific verb and resource: it computes selected celestial bodies and returns every pairwise angular separation in degrees. This clearly distinguishes it from siblings like celestial_state or celestial_event_window, which likely return different celestial outputs.

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?

The description lists broad domains where it is useful (astronomy, reconstruction, rendering, research, event planning), which implies usage context. However, it does not explicitly say when to choose this tool over alternatives such as celestial_state or celestial_event_window.

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?