Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_chandramasa

Read-onlyIdempotent

Retrieve Hindu lunar month details for a date and location, including Chandramasa name, Amanta or Purnimanta system, and lunar month start and end dates.

Instructions

Get Chandramasa (Hindu lunar month) details for a given date and location.

Returns the current Hindu lunar month name, Purnimant/Amant system, and the start/end dates of the lunar 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": {
      "params": "<params>"
    },
    "name": "divine_get_chandramasa"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYesDate, location, and timezone
month_typeNoLunar month system: 'amanta' (default, new-moon ending) or 'purnimanta' (full-moon ending)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered without description help. The description adds the returned fields (month name, Purnimant/Amant system, start/end dates), but says nothing about error behavior for invalid dates/times, timezone handling, or the fact that calls hit an external service (openWorldHint).

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?

Two short sentences, front-loaded with the purpose, no filler. The second sentence partly duplicates what the output schema already conveys, which keeps it from a 5.

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

Completeness4/5

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

With full schema coverage, annotations, and an output schema, the description is complete enough to call correctly. The remaining gap is routing versus the sibling chandramasa_list tool and any note on external-API failure modes.

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%, so both `params` and `month_type` are already documented in the schema, including the amanta/purnimanta values and the default. The description only vaguely echoes 'Purnimant/Amant system' as a return value, adding no new parameter guidance — baseline 3 is appropriate.

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 gives a specific verb+resource ('Get Chandramasa ... details') and helpfully glosses the domain term as 'Hindu lunar month', including the date/location scope. It does not, however, differentiate itself from the sibling divine_get_chandramasa_list or explain which one an agent should pick.

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

Usage Guidelines3/5

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

Usage is only implied by 'for a given date and location' — the agent can infer this is a single-date lookup, but there is no explicit when-to-use, when-not-to-use, or pointer to the _list alternative. For a domain with a near-identical sibling name, that omission matters.

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