Moment Sky

calculate_sky

Read-onlyIdempotent

Calculate bright stars and naked-eye planets, 2000–2050. Coordinates and UTC are processed without storage.

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": {
      "utc": "<utc>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "calculate_sky"
  }
}

Input Schema

Name	Required	Description
`utc`	Yes	ISO 8601 UTC with Z, 2000–2050
`latitude`	Yes
`longitude`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds one genuinely new trait not in annotations — "processed without storage" — which is useful privacy context. However, with no output schema it says nothing about what comes back (list form, units, visibility filtering), which is the main remaining behavioral gap.

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?

Two tight sentences with zero filler, and the primary purpose is front-loaded ahead of the privacy caveat. Slightly awkward phrasing in the second sentence but no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-required-parameter tool with no output schema and a sibling, the description covers purpose and data handling but omits the return shape and the differentiation an agent needs to choose correctly. Adequate as a minimum-viable definition, incomplete for this configuration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: only 'utc' has a description; latitude and longitude carry bounds but no stated units or semantics in the schema. The description's "Coordinates and UTC" and "2000–2050" merely restate the schema's existing hints rather than compensating — it never says the coordinates are decimal degrees WGS84 or that they define the observer's horizon.

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?

Specific verb ("Calculate") plus a specific resource ("bright stars and naked-eye planets") with a stated domain (2000–2050). An agent immediately knows it produces a sky/visibility computation, but nothing distinguishes it from the sibling get_free_preview.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus the sibling get_free_preview, nor any prerequisite (required location/UTC, range limits as preconditions). Usage must be entirely inferred from the verb.

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

All Moment Sky 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?