MysticAPI

sky_today

Today's universal sky: which planets are retrograde right now, the current moon phase and illumination, geocentric positions for 13 bodies (zodiac sign + Energy Blueprint gate/line), and a 30-day forward scan of retrograde stations and new/full moons. No input. Deterministic astronomy (JPL-validated ephemeris). Costs 1 call.

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": "sky_today"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description fully covers behavior: 'No input', 'Deterministic astronomy (JPL-validated ephemeris)', and 'Costs 1 call'. It is transparent about being read-only and predictable.

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 with front-loaded content: first sentence summarizes output, second confirms no input, third provides credibility and cost. Every sentence is valuable and concise.

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?

Without an output schema, the description thoroughly explains return values: retrograde planets, moon phase, positions for 13 bodies (zodiac + gate/line), and 30-day forward scan. Complete for a no-parameter tool.

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

Parameters4/5

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

No parameters exist, so baseline is 4. The description does not need to add parameter info and appropriately states there is no input.

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 description explicitly states it provides 'Today's universal sky' with specific data: retrograde planets, moon phase, geocentric positions for 13 bodies, and a forward scan. The verb is implicit but clear, and it distinguishes from siblings like 'sky_personal' by specifying 'universal' sky.

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?

The description clearly indicates 'No input' and mentions cost, implying it's for quick, deterministic sky overview. It does not explicitly contrast with alternatives like 'sky_personal', but the context suggests when to use it.

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

All MysticAPI 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?