Skip to main content
Glama
Sign In
Natal Chart Lab MCP

Natal Chart Lab MCP

by xucheng2024
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Moon phases

get_moon_phases
Read-only

Retrieves new, first-quarter, full, and last-quarter Moon dates with UTC time, zodiac degree, Earth–Moon distance, and eclipse flags for 1950–2050; defaults to next 60 days.

Instructions

New Moons, first quarters, Full Moons and last quarters in a date range, with the UTC time, zodiac sign and degree, Earth–Moon distance and any eclipse. Covers 1950–2050. Defaults to the next 60 days.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (ISO 8601). Defaults to 60 days after from.
fromNoStart date (ISO 8601). Defaults to now.
phaseNoOnly this phase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral facts — the 1950–2050 coverage boundary and that omitting dates returns the next 60 days. It does not state result ordering, maximum result counts, or what happens when the range exceeds the coverage window, which keeps it from a 5.

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, zero filler: the first front-loads what is returned and the second states coverage limits and the default window. Every clause carries information an agent needs to call it correctly.

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?

With no output schema, the description properly compensates by enumerating returned fields, and it covers the coverage window and default range for a 3-parameter read tool. Minor gaps remain on ordering, result limits, and behavior at the 1950/2050 boundaries.

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%, so the schema already explains from, to, and the phase enum with its allowed values. The description's 'defaults to the next 60 days' echoes the schema's default and adds no format syntax or filtering semantics beyond it; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource precisely (moon phase events) and enumerates the exact outputs — UTC time, zodiac sign and degree, Earth–Moon distance, eclipse flag — so an agent knows what comes back. It does not explicitly contrast itself with siblings like get_current_sky or get_planet_positions, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: 'in a date range' plus the 60-day default tells an agent this is a range query, and the phase enum hints at filtering. There is no explicit when-to-use versus get_current_sky or get_planet_positions, and no statement of when this tool is inappropriate.

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

Deploy Server

Other Tools