Asterwise

Muhurta

asterwise_get_muhurta

Read-onlyIdempotent

Searches a date span for top-scoring muhurta windows for a named activity using Panchanga, Choghadiya, and classical siddhi flags at a location.

WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_panchanga — drill into Panchanga limbs for a chosen winning date.

INPUT CONTRACT: activity must be one of the supported English slugs above — not validated locally; bad values become MCP INTERNAL_ERROR. from_date/to_date ordering and span rules are enforced upstream. Location coordinates reuse LocationInput validation for lat/lon/date pattern.

DO NOT CONFUSE WITH: asterwise_get_choghadiya — enumerates all Choghadiya for one day without activity scoring across a span. asterwise_get_panchanga — single-day limb detail, not ranked muhurta search.

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

Input Schema

TableJSON Schema

Name	Required	Description
`to_date`	Yes	End of the search window for auspicious times, YYYY-MM-DD.
`activity`	Yes	Activity to find an auspicious time for, e.g. 'marriage', 'travel', 'business opening'.
`location`	Yes	Place name, e.g. 'Chennai, India'. Alternative to giving latitude, longitude and timezone.
`from_date`	Yes	Start of the search window for auspicious times, YYYY-MM-DD.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / activity / description

Added value: +"Activity to find an auspicious time for, e.g. 'marriage', 'travel', 'business opening'."

addedInput schema / properties / from_date / description

Added value: +"Start of the search window for auspicious times, YYYY-MM-DD."

changedInput schema / properties / location / description

Previous value: -"For tools that need location but not birth time."New value: +"Place name, e.g. 'Chennai, India'. Alternative to giving latitude, longitude and timezone."

addedInput schema / properties / to_date / description

Added value: +"End of the search window for auspicious times, YYYY-MM-DD."

First observedApr 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar for added value is met by disclosing that invalid activity slugs are NOT validated locally and surface as MCP INTERNAL_ERROR, and that date ordering/span rules are enforced upstream. These are genuinely useful non-obvious behaviors beyond what annotations 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?

The description is efficiently sectioned (purpose, WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH, docs link) with the core purpose front-loaded. Each section earns its place; the labeled headers make machine parsing easy. Slightly longer than minimal, but every sentence carries either a constraint, a routing decision, or an error-behavior disclosure.

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

Completeness4/5

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

For a complex domain tool with output schema present, nested location object, and ~100 siblings, the description covers purpose, workflow, input constraints, error behavior, sibling differentiation, and points to a full documentation contract. Minor gaps: the supported activity slugs are referenced but not enumerated, and the schema's location ambiguity (place-name vs. coordinates) is not fully reconciled in the description.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by warning that activity must be one of the supported English slugs (not locally validated) and that date ordering/span rules are enforced upstream. It also notes LocationInput validation reuse for lat/lon/date, which helps an agent understand cross-tool consistency.

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?

The opening sentence states a specific verb ('Searches'), a precise resource ('date span for top-scoring muhurta windows'), and the distinguishing scope ('named activity', 'at a location', using Panchanga/Choghadiya/siddhi flags). The DO NOT CONFUSE WITH section explicitly names two siblings and explains why they differ, so an agent can discriminate without inspecting their 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?

The WORKFLOW section declares this tool is standalone (BEFORE: None) and routes to asterwise_get_panchanga afterwards, while DO NOT CONFUSE WITH names asterwise_get_choghadiya (enumerates all windows, no activity scoring) and asterwise_get_panchanga (single-day detail, not ranked search) as alternatives. This is explicit when-to-use and when-not-to-use guidance with named alternatives.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Many tools are well-differentiated by explicit 'DO NOT CONFUSE WITH' notes, but the sheer number of near-neighbor pairs (e.g., crystal vs gemstone recommendations, natal chart variants, dasha systems, compatibility systems, tarot draw variants) creates real selection risk. The descriptions mitigate overlap, but an agent browsing 103 tools will struggle to pick the right one.

Naming Consistency5/5

Every tool follows the asterwise_get_* or asterwise_draw_* prefix convention with a clear noun phrase (e.g., asterwise_get_natal_chart, asterwise_draw_tarot_cards). The two verbs 'get' and 'draw' are semantically appropriate, and there are no camelCase or mixed-style names.

Tool Count1/5

103 tools is far beyond a manageable MCP surface. While the domain is broad (Vedic astrology, Western astrology, numerology, tarot, crystals, dream symbols), the server bundles multiple distinct domains into one namespace, making it nearly impossible for an agent to discover the right tool efficiently.

Completeness4/5

The surface is impressively comprehensive across astrology, numerology, tarot, and remedies, with deep coverage of dasha systems, compatibility frameworks, and chart types. Minor gaps exist (e.g., no tarot interpretation endpoint, no batch operations, no update/delete since it's read-only data), but for a reference/prediction API the coverage is strong.

Resources

Need Help?