Asterwise

Tamil Panchanga

asterwise_get_tamil_panchanga

Read-onlyIdempotent

Tamil Panchanga for a date and location: Rahu Kalam, Yamagandam, Kuligai (Gulika), Nalla Neram and the Tamil solar month. Nalla Neram is the daytime windows free of those periods; the month comes from the Sun's sidereal sign at sunrise.

WORKFLOW: BEFORE: asterwise_geocode — when you only have a place name. AFTER: asterwise_get_panchanga — the day's limbs and other timings.

INPUT CONTRACT: date (YYYY-MM-DD), lat, lon, timezone (IANA, default Asia/Kolkata).

DO NOT CONFUSE WITH: asterwise_get_rahu_kaal — the same three periods without the Tamil month or Nalla Neram. asterwise_get_panchanga — the full panchanga day.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-tamil-panchanga/

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": {
      "date": "<date>",
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "asterwise_get_tamil_panchanga"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes	Latitude in decimal degrees, north positive.
`lon`	Yes	Longitude in decimal degrees, east positive.
`date`	Yes	Date for the Tamil panchanga, YYYY-MM-DD.
`timezone`	No	IANA timezone of the location.	Asia/Kolkata
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 28, 2026

addedInput schema / properties / date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

addedInput schema / properties / lat

Added value: +{
+  "description": "Latitude in decimal degrees, north positive.",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

removedInput schema / properties / latitude

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Latitude in decimal degrees, north positive (e.g. 13.08)."
-}

removedInput schema / properties / location

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Place name, e.g. 'Chennai, India'. Alternative to giving latitude, longitude and timezone."
-}

addedInput schema / properties / lon

Added value: +{
+  "description": "Longitude in decimal degrees, east positive.",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

removedInput schema / properties / longitude

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Longitude in decimal degrees, east positive (e.g. 80.27)."
-}

removedInput schema / properties / timezone / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / timezone / default
```
Previous value: -nullNew value: +"Asia/Kolkata"
```

changedInput schema / properties / timezone / description

Previous value: -"IANA time zone name, e.g. 'Asia/Kolkata'."New value: +"IANA timezone of the location."

addedInput schema / properties / timezone / type
```
Added value: +"string"
```

changedInput schema / required

Previous value: -[
-  "date"
-]New value: +[
+  "date",
+  "lat",
+  "lon"
+]

Changed6 schema fields changedSep 5, 2026

addedInput schema / properties / date / description

Added value: +"Date for the Tamil panchanga, YYYY-MM-DD."

addedInput schema / properties / latitude / description

Added value: +"Latitude in decimal degrees, north positive (e.g. 13.08)."

addedInput schema / properties / location / description

Added value: +"Place name, e.g. 'Chennai, India'. Alternative to giving latitude, longitude and timezone."

addedInput schema / properties / longitude / description

Added value: +"Longitude in decimal degrees, east positive (e.g. 80.27)."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

addedInput schema / properties / timezone / description

Added value: +"IANA time zone name, e.g. 'Asia/Kolkata'."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "date",
-  "response_format"
-]New value: +[
+  "date"
+]
```
AddedMay 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context by defining Nalla Neram (daytime windows free of the three periods) and the derivation of the Tamil month from the Sun's sidereal sign at sunrise, plus a link to the full output/error contract.

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?

Front-loaded with the resource and return set, then cleanly sectioned into workflow, input contract, and disambiguation. Slightly repetitive across the return enumeration and the disambiguation lines, but every block earns its place.

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

Completeness5/5

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

An output schema exists, so return values need not be explained; the description instead supplies the workflow routing, input contract, and sibling disambiguation an agent needs. For a 5-param read-only tool, nothing material is missing.

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 the schema already documents all five parameters including formats and defaults. The 'INPUT CONTRACT' line restates date format, lat/lon, and the IANA timezone default rather than adding syntax or edge-case meaning. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb+resource and enumerates exactly what it returns (Rahu Kalam, Yamagandam, Kuligai, Nalla Neram, Tamil solar month). The 'DO NOT CONFUSE WITH' block names the sibling tools it overlaps with, so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Provides an explicit BEFORE (geocode when only a place name) and AFTER (get_panchanga for the day's limbs), plus a disambiguation section contrasting it against rahu_kaal and panchanga with the condition that selects each. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?