Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_other_calendars_and_epoch

Read-onlyIdempotent

Convert a given date into Vikram Samvat, Shaka Samvat, Kali Yuga, and Julian day values for cross-calendar and epoch reference.

Instructions

Get dates in other calendar systems and epoch values for a given date.

Returns conversions to Vikram Samvat, Shaka Samvat, Kali Yuga, and Julian day numbers.

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_other_calendars_and_epoch"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld behavior. The description adds value by naming the calendar systems and Julian day output, but it does not disclose input requirements, error conditions, or other behavioral context beyond the return fields.

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 is two sentences, front-loaded with the primary action and then a concise list of return values. There is no unnecessary wording.

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 tool that requires a full PanchangInput including location and timezone, the description omits any mention of these input requirements. An output schema exists, so return values need not be explained further, but the input side is inadequately covered.

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 description coverage is reported as 0%, so the description should compensate but does not. The single 'params' object requires date, place, latitude, longitude, timezone, and language, yet the description mentions none of these required inputs.

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 states a specific verb ('Get') and resource ('dates in other calendar systems and epoch values'), and it lists the exact conversions returned. It does not explicitly differentiate itself from sibling calendar tools, but the purpose is clear and unambiguous.

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 alternatives, no prerequisites, and no exclusions. The description only implies a use case by stating what it returns.

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