Skip to main content
Glama

Astral Code

Moon phase and lunar sign

get_moon_phase
Read-onlyIdempotent

Calculate geocentric Moon phase, illumination and tropical lunar sign on a date at 12:00 UTC, or at the current instant if date is omitted. Not a local moonrise forecast or medical timing advice.

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_moon_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional YYYY-MM-DD, 1900–2100. Evaluated at noon UTC.
localeNoConversation language. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful behavior beyond them: geocentric frame, tropical zodiac convention, noon-UTC evaluation point, and default-to-now when the date is absent.

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?

Two sentences with zero filler; the positive definition and time basis come first, then the exclusions. Every clause carries information an agent needs.

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 two-parameter, fully optional read-only tool with complete schema coverage and full annotations, the description supplies everything needed: what is computed, the reference frame, the time basis, and what it must not be used for.

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?

Schema coverage is 100%, so the baseline is 3. The description nevertheless adds real meaning: it explains what happens when 'date' is omitted (current instant), a default the schema does not state, and it reinforces the noon-UTC evaluation rule rather than merely repeating field names.

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 (calculate) plus the exact resource and outputs: geocentric Moon phase, illumination and tropical lunar sign. The time basis (12:00 UTC, or now if date is omitted) and the negative scope ('not a local moonrise forecast') make it clearly distinguishable from the birth-chart siblings.

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?

Gives concrete usage context (supply a date, or omit it for the current instant) and explicit exclusions for what the tool is not meant for. It stops short of naming an alternative tool for the excluded cases, so it is clear but not a full routing rule.

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.

Resources