Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_moon_phases

Retrieve moon phases for a selected date or month from AstroChalit's Vedic astrology API; provide the date in YYYY-MM-DD format.

Instructions

Execute moon_phases AstroChalit API to get moon phases for a selected date/month

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selectedDate": "<selectedDate>"
    },
    "name": "get_moon_phases"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectedDateYesSelected date in YYYY-MM-DD format (e.g. 2024-05-15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing about what is returned (phase names, illumination percentage, timezone handling) or whether the call is read-only and side-effect free. Only the verb 'get' weakly implies a safe read. A single-parameter lookup is simple, but the return shape and date-basis behavior are left entirely unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, which is good, but 'Execute moon_phases AstroChalit API' is internal API phrasing that does not help selection. The ambiguous 'date/month' tail introduces doubt rather than value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with a fully documented schema, no nested objects, and no output schema, the description is minimally adequate. But with zero annotations and no stated return content, the definition leaves the agent guessing about the response format and whether the date is interpreted in a specific timezone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter is already documented with format and an example, and the description adds no further meaning. Worse, the description's 'date/month' wording conflicts with the schema's single YYYY-MM-DD selectedDate field, potentially leading the agent to pass month values that would fail.

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?

The description names a specific verb and resource: get moon phases for a given date. It is distinguishable from the sibling chart tools (get_moon_chart, get_divisional_chart_*) because phases are a distinct output. However, the phrase 'Execute moon_phases AstroChalit API' is implementation noise, and 'date/month' muddies the scope since the tool takes a single date.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the nearby get_moon_chart or the ephemeris tools, and no prerequisites or exclusions are stated. The agent must infer from the name alone that this is the moon-phase lookup.

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