Skip to main content
Glama
astroway

astroway-mcp

Official

Shadbala — Sthana (positional)

vedic_shadbala_sthana
Read-onlyIdempotent

Calculate Sthana Bala, the positional strength of planets in Vedic astrology, by evaluating five sub-strengths: exaltation, varga charts, odd/even sign suitability, angular houses, and drekkana.

Instructions

Sthana Bala — sum of 5 sub-strengths: Ucchabala (exaltation), Saptavargaja (sum across 7 vargas D1/D2/D3/D7/D9/D12/D30 with Mulatrikona+Own/Friend/Neutral/Enemy weights per BPHS A.27.10-19), Ojhayugmarasyamsa (odd/even sign suitability D1+D9), Kendradi (60/30/15 angular/succedent/cadent), Drekkana (1st/2nd/3rd third gender match).

[Group: Vedic] [Cost: 50 credits (Tier 3)]

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
timeYes
timezoneOffsetNo
latitudeNo
longitudeNo
houseSystemNoP
nameNo
cityNo
zodiacTypeNo
ayanamsaIdNo
cosmogramNo
Behavior3/5

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint. The description adds no behavioral traits beyond the calculation details, which is acceptable given the annotations.

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 front-loaded with purpose and includes detailed sub-strength information. It is concise for the technical content, though slightly lengthy.

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

Completeness2/5

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

There is no output schema, and the description does not explain return values or structure. For a complex Vedic tool, this is a significant gap.

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

Parameters1/5

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

The input schema has 11 parameters with 0% description coverage. The tool description only provides an example body without explaining any parameter meaning, usage, or constraints.

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 description clearly states that the tool computes Sthana Bala, a component of Shadbala, listing the five sub-strengths with specific references. This distinguishes it from sibling tools like vedic_shadbala_cheshta and vedic_shadbala_dig.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus other Shadbala tools or alternatives. The description lacks any context about specific use cases or exclusions.

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