Skip to main content
Glama
astroway

astroway-mcp

Official

Shadbala — Cheshta (motional)

vedic_shadbala_cheshta
Read-onlyIdempotent

Calculates Cheshta Bala, the motional strength of planets in Vedic astrology using retrograde status and speed. Outputs a value for chart interpretation.

Instructions

Cheshta Bala — motional strength via simplified retrograde+speed model: retrograde=60v, direct slow=ratio*60, direct fast=(2-ratio)*60. Sun=0 (handled via Ayana with ×2), Moon=0 (handled via Paksha with ×2). Full BPHS Cheshta-Kendra method (mean-longitude based) queued for Phase Q — current divergence vs jhora ≤30v on non-stationary dates.

[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
Behavior4/5

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

Annotations already indicate read-only, no destruction, idempotent. Description adds behavioral details: simplified model, specific retrograde/speed formulas, Sun/Moon=0, divergence vs jhora ≤30v. This provides useful context beyond 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?

Description is relatively concise and front-loaded with the purpose and key formula. The example request body is useful. However, the technical formula details could be moved to parameter description for better structure.

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?

With 11 parameters and no output schema, the description should provide better guidance on parameters and expected output. The example helps but is insufficient for a complete understanding.

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?

Schema description coverage is 0%. Description does not explain any parameter semantics despite 11 parameters. Only shows an example request body without explaining what each parameter means or how to set them.

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 defines itself as Cheshta Bala (motional strength) and distinguishes from other shadbala components. Uses specific verb 'computes' implied, and states it's a simplified retrograde/speed model.

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?

No explicit when-to-use or when-not-to-use guidance. Mentions future 'Full BPHS Cheshta-Kendra method' but does not clarify when the current simplified version is appropriate vs other tools.

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