Moon Phase Software

Full Moons of a year

find_full_moons

Read-onlyIdempotent

Returns every full Moon of a calendar year with its date and time in a time zone, its traditional name such as Wolf Moon or Harvest Moon, its distance from Earth and whether it is a supermoon or a Blue Moon. Years run from 1900 to 2100.

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

Input Schema

Name	Required	Description	Default
`year`	No	Calendar year from 1900 to 2100; the current year when omitted.
`timeZone`	No	IANA time zone name such as America/New_York or Asia/Tokyo; UTC when omitted.

Output Schema

Name	Required	Description	Default
`view`	Yes
`items`	Yes
`total`	Yes
`request`	Yes
`pageSize`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/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), so the description's added value is the hard 1900-2100 year boundary and the disclosure that results include supermoon and Blue Moon classification plus Earth distance. That is real behavioral context beyond the structured fields, though it says nothing about ordering of results within the year or result-size behavior.

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, front-loaded with the return contract and finished with the constraint. Every clause carries information; there is no filler or restatement of the tool name.

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?

With an output schema present, the description need not describe return structure, and annotations plus the schema cover safety and both parameters fully. For a two-parameter read tool, nothing an agent needs in order to call it correctly 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 coverage is 100% and both parameters document their defaults (current year, UTC) in the schema itself. The description's "Years run from 1900 to 2100" merely restates the schema's minimum/maximum and adds no format or interpretation detail beyond it, so the baseline 3 applies.

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 ("Returns every full Moon of a calendar year") and then enumerates exactly what each entry carries: date/time in a time zone, traditional name, distance from Earth, and supermoon/Blue Moon status. That enumeration naturally separates it from a single-phase tool like get_moon_phase or a broader get_moon_calendar without needing to name them.

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 by the resource scope; there is no explicit statement of when to prefer this over get_moon_calendar or get_moon_phase, nor any prerequisites or exclusions. An agent can infer this is the per-year full-Moon listing, but the description does no active routing.

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

All Moon Phase Software tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.