Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Muhurat: Naming ceremony (Namkaran)

astroway_vedic_muhurat_naming_ceremony
Read-onlyIdempotent

Find auspicious days for a Namkaran naming ceremony by scanning a supplied date window and returning ranked muhurat options based on nakshatra acceptance.

Instructions

Auspicious-window scanner for Namkaran (naming ceremony). Wide nakshatra acceptance per classical text. Note: orthodox practice schedules Namkaran on the 11th or 12th day after birth; this scan returns top auspicious days within any caller-supplied window.

[Group: Vedic] [Endpoint: POST /v1/vedic/muhurat/naming-ceremony] [Required: search_window_start] [Cost: 50 credits (Tier 3)]

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": {
      "search_window_start": "<search_window_start>"
    },
    "name": "astroway_vedic_muhurat_naming_ceremony"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNNo
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeNo
longitudeNo
ayanamsaIdNo
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC.
search_window_endNo
search_window_startYes

Output Schema

NameRequiredDescriptionDefault
activityNo
ayanamsaNo
locationNo
search_windowNo
auspiciousWindowsNo
nextAuspiciousWindowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavior: results are bounded to the caller-supplied window, wide nakshatra acceptance follows classical text, and the call costs 50 credits (Tier 3). It does not describe pagination or how many days are typically returned, but the window-bounding caveat is the important disclosure.

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?

Three sentences, front-loaded with the purpose, then the classical-text qualifier, then the practical scheduling caveat. The bracketed metadata block (group, endpoint, required, cost) is boilerplate but compact and useful; no sentence is wasted.

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

Completeness3/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, and annotations cover safety, but for an 8-parameter tool with 25% schema coverage the description leaves coordinate defaults and the result-count control unaddressed. Enough to call it correctly for the happy path, not enough for a careful agent.

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?

With only 25% schema coverage, the description partially compensates by calling out '[Required: search_window_start]' and framing the scan as operating on a caller-supplied window. It says nothing about latitude/longitude defaulting to 0 (a real trap), topN, ayanamsa choice, or the meaning of search_window_end, leaving most of the 8 parameters undocumented.

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

Purpose4/5

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

The description states a specific verb+resource: an auspicious-window scanner for Namkaran (naming ceremony), with the domain term glossed in English. It distinguishes itself from the many other muhurat siblings purely by the named ceremony rather than by an explicit comparison, so it is clear but not sibling-differentiating.

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

Usage Guidelines3/5

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

Usage is implied by the ceremony name and the note that the scan returns top days within any caller-supplied window, but there is no explicit when-to-use/when-not guidance against near neighbors such as astroway_vedic_muhurat_name_change or astroway_vedic_muhurat_general_auspicious. The orthodox 11th/12th-day remark is useful domain context but not a routing rule.

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

Deploy Server

Other Tools