Skip to main content
Glama
astroway

astroway-mcp

Official

Varga D9 — Navamsa

vedic_varga_D9
Read-onlyIdempotent

Generate the Navamsa (D9) chart for Vedic astrology analysis of spouse, marriage, and dharma using birth date, time, and location.

Instructions

Navamsa chart (spouse, dharma; the most important divisional chart in BPHS Vedic analysis).

[Group: Vedic] [Cost: 20 credits (Tier 2)]

Example request body: {"date":"1990-05-15","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date YYYY-MM-DD
timeYesBirth time HH:mm:ss (local)
timezoneOffsetNoUTC offset in hours (e.g. 3 for UTC+3, -5 for EST)
latitudeNoBirth latitude in decimal degrees
longitudeNoBirth longitude in decimal degrees
houseSystemNoHouse system: P=Placidus (default), K=Koch, W=Whole Sign, E=Equal
cityNoCity name (display only)
Behavior3/5

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

Annotations already declare read-only and idempotent. The description adds the cost (20 credits) but no further behavioral traits. Does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: two sentences, no fluff, includes group and cost info. Front-loads the core purpose.

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?

Given the large number of sibling tools (many vedic_varga_D*), the description lacks details about output format or how this varga relates to others. Minimal context for selection.

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?

Schema covers all 7 parameters comprehensively (100% coverage). The description does not add any additional semantic value beyond what is 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?

Clearly states it's the Navamsa chart and identifies it as the most important divisional chart, with keywords 'spouse, dharma'. This distinguishes it from other vedic_varga siblings.

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?

Implies usage for marital and dharma analysis but provides no explicit guidance on when to use this varga over others among the many siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server