Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_samvat

Read-onlyIdempotent

Retrieve Vikram and Shaka Samvat year names and numbers for a specific date and location to identify the Hindu calendar year.

Instructions

Get Samvat (Hindu calendar year) details for a given date and location.

Returns the current Vikram Samvat, Shaka Samvat year names and 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_samvat"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and idempotency profile is fully covered without the description. The description adds only that both Vikram and Shaka Samvat values are returned, which is largely restated by the output schema; nothing is said about failure modes for invalid dates or unsupported locations.

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

Conciseness5/5

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

Two short sentences, purpose front-loaded, with the return values second. No filler or repetition of the tool name alone.

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 read-only lookup with a rich output schema and fully documented nested parameters, the definition covers the essentials. The missing piece is routing guidance against the dense set of sibling panchang/calendar tools, which matters for correct tool selection in this catalog.

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?

The description mentions only "date and location" and gives no detail on tzone, lat/lon format, or the non-ISO language codes. However, the nested PanchangInput $defs in the schema does document every field thoroughly (including the unusual 'ma'/'tm'/'tl' language codes), so the agent is not left guessing even though the description itself adds nothing.

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 Samvat (Hindu calendar year) details") and even enumerates the returned values (Vikram Samvat and Shaka Samvat names/numbers), so the agent knows exactly what the tool produces. It does not, however, contrast itself with closely related calendar siblings such as divine_get_chandramasa or divine_get_ghata_chakra.

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?

The only usage framing is the input scope ("for a given date and location"). There is no statement of when this tool should be selected over the many other Hindu-calendar and panchang tools in the sibling list, and no exclusions or prerequisites.

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