Thirumana Porutham
asterwise_get_thirumana_porutham
Evaluates twelve Tamil Thirumana poruthams for two charts, tracks veto severity for Rajju, and returns an expanded breakdown map with tradition metadata.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
person1 | object | yes | Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa |
person2 | object | yes | Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa |
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
What it covers
Extends the ten-porutham screen with Nadi and Varna plus richer Rajju severity coding (5=Siro most severe, down to 1=Pada least severe) and labels. Same veto booleans as shorter Tamil tools. Not Ashtakoota (asterwise_get_compatibility) nor Dashakoot (asterwise_get_dashakoot).
Workflow
BEFORE: RECOMMENDED — asterwise_get_porutham — quick ten-koota pass before twelve-koota depth.
AFTER: None.
Input
Two BirthData objects per global contract.
Output contract
data.total_passed (int — out of 12)
data.total_poruthams (int — 12)
data.compatibility_level (string)
data.rajju_veto (bool)
data.vedha_veto (bool)
data.hard_veto (bool)
data.rajju_severity (int — 5=Siro most severe, 4=Kantha, 3=Udara, 2=Kati, 1=Pada least severe)
data.rajju_severity_label (string — body part name)
data.tradition (string — 'Tamil Thirumana Porutham')
data.breakdown{} — twelve keys with full porutham names (e.g. 'Gana Porutham'):
passed (bool)
plus type-specific fields following the same patterns as asterwise_get_porutham (counts, scores, rajju pairs, vedha flags, etc.)
Response format
response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.
Compute class
MEDIUM_COMPUTE
Errors
INVALID_PARAMS (local — caught before upstream call):
None — all validation is upstream.
INVALID_PARAMS (upstream):
— None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— rajju_severity encodes body-zone risk — pair with rajju_veto boolean.
Do not confuse with
asterwise_get_porutham — ten poruthams only, no Nadi/Varna keys.
asterwise_get_compatibility — North Indian 36-point schema, not Tamil porutham map.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.