Get upcoming moon phases (New Moon, First Quarter, Full Moon, Last Quarter) and current moon illumination percentage from the US Naval Observatory.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Start date in YYYY-MM-DD format (default: today) | |
| count | No | Number of phases to return (default: 4, max: 99) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden but only states it retrieves data from the US Naval Observatory. It lacks details on side effects, caching, or latency, but is adequate for a read-only tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence that immediately conveys the tool's purpose, with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with two parameters and no output schema. The description covers the purpose and data source, remaining concise and complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both parameters are well-documented in the schema. The description does not add additional meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves upcoming moon phases and current illumination, but it does not explicitly distinguish from siblings like 'get_astronomy' or 'get_current_time'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect: get_astronomy handles daily sun/moon times, get_current_time provides current time in any timezone, and get_moon_phases covers moon phases and illumination. There is no functional overlap.
All tools follow the consistent pattern 'get_<noun>' with snake_case, making the naming predictable and readable.
With only three tools, the server is lean but covers core time and astronomy queries. The count is at the lower end of reasonable, but not overly thin.
The toolkit covers essential time and astronomy needs (current time, sun/moon times, moon phases), but lacks time zone conversion, planetary data, or specific date queries for astronomy events, representing minor gaps.