Skip to main content
Glama

Sky right now

get_sky
Read-only

Returns where the Sun, the Moon and the planets are now or at a given moment, with the Moon's phase. It fits a question about the sky at one moment, with no person's chart involved. It is astronomy only and makes no personal prediction. Moments run from 1800 to 2199. It takes an optional time zone; without one its times are in UTC. It gives positions for a moment, with no houses or rising sign.

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

Input Schema

NameRequiredDescriptionDefault
zoneNoThe person's time zone, such as Asia/Bangkok or America/New_York. Without it, times are in UTC.
bodiesNo
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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-schema behavior: the supported moment range 1800–2199, UTC as the default when no zone is given, and the absence of houses or a rising sign. With annotations carrying the safety burden, this added context puts it slightly above the midpoint.

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 return payload is front-loaded in the first sentence, followed by usage framing and constraints. The closing sentence ('gives positions for a moment, with no houses or rising sign') partly restates the earlier no-chart point, a small redundancy in an otherwise tight definition.

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 values need not be explained, and the year bounds and UTC default fill the main behavioral gaps for a read-only positional lookup. The only meaningful omission is the default behavior when 'bodies' is omitted, given all three parameters are optional.

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 67%, so zone and instant are already documented in the schema. The description reinforces the zone default (UTC without one) and implies what 'instant' means by 'now or at a given moment', but it never explains what omitting 'bodies' returns, which is the one parameter with no schema description at all.

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 opens with a concrete verb and resource set: it returns the positions of the Sun, Moon and planets plus the Moon's phase, either now or at a supplied moment. It then scopes itself against the chart-oriented siblings by stating that no person's chart, houses or rising sign are involved, so an agent can separate it from natal/transit tools 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 Guidelines4/5

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

It states the fitting question ('the sky at one moment, with no person's chart involved') and rules out personal prediction, which tells the agent when this tool is appropriate. It does not name a specific alternative for the chart case, so the routing is by concept rather than by explicit sibling reference.

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.