Skip to main content
Glama
Sign In

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

Western Moon Calendar

asterwise_get_western_moon_calendar
Read-onlyIdempotent

Returns lunar phase data for every day in a calendar month as a structured array. Each element is a complete daily phase object identical to asterwise_get_western_moon_phase.

WORKFLOW: BEFORE: None — standalone. AFTER: None.

INPUT CONTRACT: year (optional int, 1-3000) — Target year. Defaults to the current year (UTC). Example: 2026 month (optional int 1–12) — Target month. Defaults to the current month (UTC). Example: 5 (May) Values outside 1–12 are rejected locally with MCP INVALID_PARAMS.

DO NOT CONFUSE WITH: asterwise_get_western_moon_phase — single-day phase only.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-moon-calendar/

Input Schema

NameRequiredDescriptionDefault
yearNoFour-digit year, 1-3000. Defaults to the current year (UTC).
monthNoMonth number 1-12. Defaults to the current month (UTC).
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / month / description
      Previous value: -"Month number 1-12. Defaults to the current month when omitted."New value: +"Month number 1-12. Defaults to the current month (UTC)."
    • changedInput schema / properties / year / description
      Previous value: -"Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted."New value: +"Four-digit year, 1-3000. Defaults to the current year (UTC)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / month / description
      Added value: +"Month number 1-12. Defaults to the current month when omitted."
    • addedInput schema / properties / response_format / description
      Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."
    • addedInput schema / properties / year / description
      Added value: +"Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted."
  3. Changed2 schema fields changed
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • removedInput schema / required
      Removed value: -[
-  "response_format"
-]
  4. Added

TDQS

A4.6/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 genuinely new behavior: out-of-range month values are rejected locally with MCP INVALID_PARAMS, and defaults resolve against UTC. It stops short of documenting output shape or rate limits, but a link to the full output/error contract partially compensates.

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?

Front-loaded purpose sentence followed by clearly labeled WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH blocks — easy to scan. Minor redundancy: the year range and defaults appear in both the description and the schema, and the BEFORE/AFTER block is nearly empty, though it does assert standalone use.

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?

An output schema exists, so return values need not be spelled out, and the description still points to a full output/error contract. Combined with param defaults, validation behavior, and sibling routing, nothing an agent needs in order to call this correctly is missing.

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, but the description adds value beyond the schema: concrete example values (2026, 5 for May) and the fact that month values outside 1–12 fail locally with MCP INVALID_PARAMS. That validation semantics is not expressed in the schema itself.

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 first sentence states a precise verb and resource with scope: lunar phase data for every day in a calendar month, returned as a structured array. It also equates the element shape to a named sibling, so an agent immediately knows what it produces and how it differs from the single-day tool.

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

Usage Guidelines5/5

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

Explicit routing is provided: 'DO NOT CONFUSE WITH: asterwise_get_western_moon_phase — single-day phase only' names the alternative and the condition that selects it. The WORKFLOW block (BEFORE/AFTER: None — standalone) further clarifies it needs no prior tool call or follow-up.

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

All Asterwise toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources