VALUE Verdicts

Celestial angular event window

celestial_event_window

Read-only

Searches a bounded UTC range for the requested angular separation between exactly two selected bodies, then refines each detected crossing to the calculator minute. It uses a fixed, owner-operated ephemeris calculator with at most 48 samples and four concurrent requests. Geometry only: no prediction or interpretation. 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": {
      "startUtc": "<startUtc>",
      "endUtc": "<endUtc>",
      "bodies": "<bodies>",
      "targetDegrees": "<targetDegrees>"
    },
    "name": "celestial_event_window"
  }
}

Input Schema

Name	Required	Description
`bodies`	Yes	Exactly two distinct supported body names.
`endUtc`	Yes	UTC end time, exactly YYYY-MM-DDTHH:mmZ; within seven days.
`_payment`	No	x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used.
`startUtc`	Yes	UTC start time, exactly YYYY-MM-DDTHH:mmZ.
`stepMinutes`	No	Optional sampling interval from 60 to 1440 minutes; default 240. Range and step may not exceed 48 samples.
`targetDegrees`	Yes	Requested angular separation from 0 to 180 degrees.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the read-only and closed-world annotations, the description discloses operational behavior: a fixed owner-operated ephemeris calculator, at most 48 samples, four concurrent requests, refinement to the calculator minute, and geometry-only output. It also gives pricing and payment context, which is unusually valuable for invocation planning.

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?

The description is front-loaded with the core operation, then adds precision, operational limits, scope, and pricing in compact sentences. Every sentence carries useful information, and there is no repetition or filler.

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 tool with full schema coverage, no output schema, and annotations covering safety, the description supplies the missing operational, cost, and scope context. It implies crossings are returned but does not specify the return payload, which is the main remaining gap.

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 input schema already documents bodies, start/end UTC, stepMinutes, targetDegrees, and payment. The description reinforces the exactly-two-bodies and angular-separation semantics but does not add material parameter-level detail 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 states a specific verb and resource: searching a bounded UTC range for an angular separation between exactly two selected bodies, refining crossings to the minute. This clearly distinguishes it from generic celestial state or relation tools, though it does not explicitly name or contrast with any sibling tool.

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

Usage Guidelines4/5

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

It gives clear usage context: bounded UTC range, exactly two bodies, angular separation, and the boundary 'Geometry only: no prediction or interpretation.' It does not explicitly name alternatives such as celestial_relations or celestial_state, so the agent must infer sibling selection from the purpose rather than from an explicit routing rule.

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?