Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_calculate_ephemeris

Generate monthly planetary ephemeris data for a specified year and month, including zodiac system and timezone options, to support Vedic astrology calculations.

Instructions

Execute calculate_ephemeris AstroChalit API

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": {
      "selectedMonthNumber": "<selectedMonthNumber>",
      "selectedYear": "<selectedYear>"
    },
    "name": "get_calculate_ephemeris"
  }
}

Input Schema

NameRequiredDescriptionDefault
zodiacNoZodiac system (Default: 'Tropical')Tropical
timeZoneNoTimezone (Default: 'Asia/Kolkata')Asia/Kolkata
selectedYearYesYear (e.g. 2024 to 2040)
selectedMonthNumberYesMonth number (1-12)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it says nothing about permissions, rate limits, data source, or response shape. The single sentence merely names an underlying API.

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

Conciseness2/5

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

The sentence is short but wasteful in the wrong direction: it is under-specified rather than concise, and the reference to "AstroChalit API" conveys no actionable information to the agent.

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

Completeness2/5

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

For a domain-specific astrology tool with no output schema and no annotations, the description should at least indicate what ephemeris data is returned (planetary positions over a month?). The complete input schema is the only thing making the tool callable at all.

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 description coverage is 100%, with zodiac enum, timezone default, year range, and month bounds all documented in the schema itself. The description adds nothing beyond the schema, which is acceptable given the complete schema, but earns no credit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name ("Execute calculate_ephemeris AstroChalit API") without explaining what an ephemeris is or what data the tool returns. It adds no distinguishing detail beyond the name, so an agent cannot tell it apart from siblings like get_calculate_planet_ingress.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling astrology tools. The agent is left to infer usage entirely from the name.

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