Asterwise

Prashna Chart

asterwise_get_prashna_chart

Read-onlyIdempotent

Casts a Prashna chart for the query instant from the supplied date, time, place and a single-topic keyword. Returns houses, Moon diagnostics, a verdict, and cusps.

WORKFLOW: BEFORE: None — standalone for horary. AFTER: None.

INPUT CONTRACT: question must be exactly one of: self, wealth, siblings, property, children, health, marriage, death, travel, career, gains, loss. Full sentences are not validated locally and are rejected upstream → MCP INTERNAL_ERROR at the tool layer. PrashnaInput enforces date/time/lat/lon/ayanamsa patterns locally.

DO NOT CONFUSE WITH: asterwise_get_natal_chart — requires birth data, not query-moment prashna. asterwise_get_kp_chart — natal KP from birth time, not horary keyword mapping.

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

Input Schema

Name	Required	Description	Default
`prashna`	Yes	Prashna (horary) query parameters.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / prashna / properties / date / description

Added value: +"Date the question was asked, YYYY-MM-DD, local to `timezone`."

addedInput schema / properties / prashna / properties / time / description

Added value: +"Time the question was asked, HH:MM (24h), local to `timezone`."

addedInput schema / properties / prashna / properties / timezone

Added value: +{
+  "default": "Asia/Kolkata",
+  "description": "IANA timezone of date and time, e.g. 'Asia/Kolkata', 'Europe/London'. Default: Asia/Kolkata",
+  "type": "string"
+}

First observedApr 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, but the description goes well beyond: it discloses the failure mode for an invalid question (rejected upstream → MCP INTERNAL_ERROR at the tool layer) and which fields are validated locally. That error contract is exactly the kind of extra behavioral context annotations cannot convey.

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 purpose followed by clearly labeled WORKFLOW / INPUT CONTRACT / DO NOT CONFUSE sections — well structured and scannable. Slightly padded by the two "None" lines and a docs URL, but no sentence is misleading and most content 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 only be summarized (they are), and annotations carry the safety profile. Combined with the error contract, sibling routing, and full keyword enum, an agent has everything needed to select and call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for date/time/lat/lon/ayanamsa, but the schema leaves `question` as a bare string (minLength 1). The description supplies the missing closed vocabulary — the exact twelve accepted topic keywords — which is essential to invoke the tool correctly and is nowhere in the schema.

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 ("Casts") and resource ("Prashna chart") plus its defining scope: the query instant from date/time/place and a single-topic keyword. It also previews the return contents (houses, Moon diagnostics, verdict, cusps) and names the siblings it is not, so an agent can distinguish it without opening any schema.

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?

The WORKFLOW block declares BEFORE/AFTER as None (standalone), and the DO NOT CONFUSE WITH section explicitly routes away from asterwise_get_natal_chart (needs birth data) and asterwise_get_kp_chart (natal KP, not horary keyword). When-to-use and when-not-to-use are both spelled out.

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?