Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Muhurat: Business start (Vyapara)

astroway_vedic_muhurat_business_start
Read-onlyIdempotent

Find auspicious Vedic muhurat windows to start a business or new venture by scanning dates for preferred nakshatras and avoiding Sun, Tuesday, and Saturday starts.

Instructions

Auspicious-window scanner for starting a business / new venture. Preferred nakshatras: Pushya/Hasta/Chitra/Anuradha/U.Phalguni/U.Ashadha/U.Bhadrapada/Sravana/Punarvasu. Avoid Sun/Tue/Sat. Same scoring shape.

[Group: Vedic] [Endpoint: POST /v1/vedic/muhurat/business-start] [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_business_start"
  }
}

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

B3.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses cost (50 credits, Tier 3), the HTTP endpoint, the required parameter, and the classical selection criteria applied to results. That is meaningful added context for a paid, read-only scan. It still doesn't say how many windows come back or whether a lower `topN` reduces cost.

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 with the purpose, then crisp domain rules, then bracketed operational metadata. Efficient overall, though the trailing 'Same scoring shape' is an opaque cross-reference that adds little to a standalone caller.

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 the cost/endpoint block is helpful. But for an 8-parameter tool with 25% schema coverage, the definition leaves the agent guessing about the end of the window, topN behavior, and geographic defaults, which is a real gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 25% (7 of 8 parameters are undocumented in the schema) and the description adds almost nothing: it names only `search_window_start` as required. Nothing explains `search_window_end`, `topN`, latitude/longitude defaults of 0, or the ayanamsa vs ayanamsaId duality, all of which materially affect results.

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?

States a specific verb+resource: an auspicious-window scanner for starting a business / new venture, which cleanly separates it from the many sibling muhurat variants (marriage, surgery, vehicle purchase, travel). It does not explicitly distinguish itself from adjacent tools like astroway_vedic_muhurat_general_auspicious or astroway_business_electional_day, so it stops short of a 5.

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 name and the 'business / new venture' framing, and domain selection rules (preferred nakshatras, avoid Sun/Tue/Sat) are given. However, there is no explicit 'use this instead of X when Y' routing against the general muhurat tool or the business electional-day tool, and no note on prerequisites such as supplying a search window.

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