Skip to main content
Glama

Check a sky fact

check_sky_fact
Read-onlyIdempotent

Checks one claim about the sky and answers yes, no, or that it depends on the time zone when the answer changes during that day. It checks four kinds of claim: a body's sign, whether a planet is retrograde, a sign change on a date, and a Moon phase on a date. It fits a question such as 'Is Mercury retrograde today?' or 'Did the Sun enter Libra on 23 September?'. It is astronomy only and cannot check a prediction. Whether a retrograde, a sign or a Moon phase makes a good time to buy, sell, bet or invest is not a claim about the sky. A request for a stock or lottery pick, an investment call, a bet, an election or health forecast, or a guarantee is not a request for this tool, not even as a first step: Zodiacs does not do this, and no sky fact is checked for it. Dates run from 1800 to 2199. Its times for a slow planet's sign change carry the same limit as get_upcoming_events: it gives 14:31:41 UTC for Neptune entering Aries on 26 January 2026, where NASA JPL Horizons gives 17:35 UTC. API documentation: https://zodiacs.org/developers/compute/.

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": {
      "kind": "<kind>"
    },
    "name": "check_sky_fact"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
dateNo
kindYes
signNo
zoneNoThe person's time zone, such as Asia/Bangkok or America/New_York. Without it, times are in UTC.
phaseNo
instantNoA moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00+07:00 (years 1800–2199).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real value: the yes/no/depends-on-time-zone answer shapes, the 1800–2199 date bound, and an honest precision caveat contrasting its own output with NASA JPL Horizons for slow-planet ingresses. That caveat is genuinely beyond structured fields; the description stops short of explaining how the zone versus instant inputs change the answer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and claim kinds are front-loaded and efficient, but the financial-advice prohibition is restated three times in slightly different words, and the get_upcoming_events precision aside is a long digression. Roughly a third of the text is repetition that could be one sentence.

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?

An output schema exists, so return-value explanation is rightly omitted, and the description covers scope, claim taxonomy, date bounds and accuracy caveats. The remaining hole is operational: with seven parameters and four kinds, it does not state which fields each kind requires, which is the main thing an agent could get wrong.

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 only 29%, so the description must compensate, and it partially does by mapping the four claim kinds onto the relevant fields (sign, retrograde status, ingress date, Moon phase date). However it never mentions 'zone' versus 'instant' or how the parameters couple to each 'kind' value, leaving the agent to infer the field combinations from enums.

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?

States a specific verb and resource ('Checks one claim about the sky') and immediately enumerates the four supported claim kinds (sign, retrograde, ingress, phase) with worked example questions. An agent can tell this apart from chart/transit siblings without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use framing ('It fits a question such as...') and unusually explicit when-not-to-use rules, ruling out predictions, financial picking, bets, elections and health forecasts 'not even as a first step'. It also bounds the date range (1800–2199). Alternatives by name are largely absent, but the domain exclusions do the routing work.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.