Skip to main content
Glama

Asteria: Astrology & Tarot

Today's sky and Moon phase

sky_today
Read-onlyIdempotent

The astrology of a day (default today): the signs of the Sun and the Moon, the Moon phase named for that day and its lit fraction, the next new moon and full moon with their signs and whether either is an eclipse, and what the current phase means. For questions about today's astrology, the Moon today or the next full moon. It does not depend on a birth chart.

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

NameRequiredDescriptionDefault
dateNoThe day, YYYY-MM-DD (default: today).
languageNoLanguage of the readings: en, fr, es, pt-BR, ja or de (default en). Use the language of the conversation.
timezoneNoIANA time zone used to cut the day (default UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no output schema, the description carries the burden of describing results, and it does so thoroughly: it lists every returned element including eclipse flags and phase meaning. Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile needs no restating, and the description correctly avoids repeating it. Minor gaps: no mention of error behavior for malformed dates or how a timezone shift can change the reported day.

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 core payload is front-loaded in the first sentence as a tight enumeration of return fields, followed by usage and scope caveats in short sentences. The long middle clause is dense but every element listed is a genuine return value, so little is wasted; a slightly shorter field list would still convey the same.

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?

For a three-optional-parameter, read-only tool with no output schema, the description supplies exactly what is needed: what is returned, that the date defaults to today, that the day is a day-level computation, and that no birth chart is required. Nothing an agent needs to call it correctly or interpret the response is missing.

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%, and each parameter already documents its default (date defaults to today, language defaults to en, timezone defaults to UTC). The description reinforces that the target is 'a day (default today)' but adds no format, syntax, or edge-case detail beyond the schema. At full coverage a baseline 3 is the correct ceiling here.

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 names a concrete resource (the astrology of a day) and enumerates exactly what it covers: Sun and Moon signs, the named Moon phase with lit fraction, the next new and full moons with signs and eclipse status, and an interpretation of the current phase. It also states a negative property ('It does not depend on a birth chart') that separates it from birth_chart, so an agent can distinguish it from siblings without opening any 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 gives explicit question-shaped triggers: 'For questions about today's astrology, the Moon today or the next full moon.' That is clear context for when to reach for this tool, and the no-birth-chart note steers agents away from natal-chart tools. It stops short of naming a specific alternative sibling (e.g. moon_sign) as the choice for a non-today sign lookup, so the exclusion side is only implied.

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.