Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Moon phase: the moon phase and illumination for a date

moon
Read-only

Moon phase name, illuminated percentage and age in days for any date, plus the next new and full moon (UTC, to the minute). Computed locally from the Moon's and Sun's orbital terms; the times agree with published almanacs within about a minute. Use for calendars and night-sky planning. Example: date=2026-10-18. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate or ISO time (default now)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

This is an exceptionally detailed description that goes far beyond annotations. It explicitly details the methodology ('computed locally from the Moon's and Sun's orbital terms'), the accuracy ('agree with published almanacs within about a minute'), and operational constraints (pricing, failure policy, write-safety).

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 description packs a large amount of diverse information (functionality, accuracy, cost, usage) into a dense but well-structured single block. Every sentence serves a highly specific purpose, though it could be slightly more segmented for readability.

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?

Without an output schema, the description must define what the tool returns, and it enumerates every single data point: phase name, percentage, age in days, and specific next moon dates/times. This makes the description highly complete for an AI agent to understand the expected result.

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?

Since the input schema coverage is 100%, the semantic burden is low. The description merely provides a format example ('date=2026-10-18'), which confirms the string format already established in the schema. The baseline 3 is appropriate given high schema coverage and minimal semantic gain in the text.

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 is highly specific, clearly stating it provides moon phase name, illumination percentage, age in days, and timing for next new/full moons. It uses specific scientific inputs (orbital terms) to define its domain, distinguishing it from general time tools.

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?

The description offers clear context by stating it is for 'calendars and night-sky planning,' which helps the agent determine applicability. It also clarifies that it is a computation/read-only tool, setting expectations for idempotent behavior.

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.