Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Auspicious windows (muhūrta) in a date range

find_muhurta
Read-onlyIdempotent

Use this when the user asks for an auspicious date or time (muhūrta) to do something, such as a wedding, launch, move or purchase, within a date range at a given place. Scans each day in the range and ranks windows for the subject. The pañcāṅga is computed for eventPlace, never defaulted to the birthplace. Cost: 10 credits per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Deterministic: the same input always gives the same answer. Example arguments: {"subject":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209},"eventPlace":{"latitude":19.076,"longitude":72.8777,"timezone":"Asia/Kolkata","label":"Mumbai"},"freeText":"signing a lease","rangeStart":"2026-11-01","rangeEnd":"2026-11-15"}

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": {
      "subject": "<subject>",
      "eventPlace": "<eventPlace>",
      "rangeStart": "<rangeStart>",
      "rangeEnd": "<rangeEnd>"
    },
    "name": "find_muhurta"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNNoHow many ranked windows to return. Default 5.
eventIdNoEvent type identifier, if known.
subjectYesBirth data of the person the event is for; windows are ranked against their chart.
freeTextNoThe event described in words, when there is no eventId.
rangeEndYesLast date to search, YYYY-MM-DD.
timeOfDayNoLocal time (HH:MM) at which each day is evaluated. Default: local sunrise.
eventPlaceYesWhere the event will happen: latitude, longitude and IANA timezone. The pañcāṅga is computed here, never at the birthplace.
rangeStartYesFirst date to search, YYYY-MM-DD.
subjectNameNoOptional name of the subject, used only in the response text.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds real behavioral context beyond the annotations: credit pricing with the sandbox exception, deterministic/idempotent output, and the critical pitfall that the pañcāṅga is computed at eventPlace and never defaults to the birthplace. That last point is exactly the kind of subtle behavior an agent cannot infer from schema.

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?

Purpose is front-loaded, followed by scan behavior, the eventPlace pitfall, cost, determinism and an example. Every line carries information, though the long inline example makes it denser than strictly necessary.

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?

For a 9-parameter tool with nested objects, the description covers trigger conditions, ranking behavior, the geographic pitfall, cost and determinism; return values are carried by the existing output schema, so nothing an agent needs is missing.

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 goes further by supplying a full example argument object that shows the nested subject/eventPlace shapes in practice. It doesn't add much semantic detail on topN, timeOfDay or eventId beyond the schema, keeping it below a 5.

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 and resource ('find auspicious windows / muhūrta in a date range') and pairs it with a concrete trigger (wedding, launch, move, purchase), which cleanly separates it from generic timing siblings like resolve_timing or get_venture_timing.

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

Usage Guidelines4/5

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

The opening sentence gives an explicit when-to-use condition with example scenarios. It stops short of naming a competing sibling or stating when NOT to use it, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.