Skip to main content
Glama
asterwise

Asterwise

Official

Varshaphal Saham

asterwise_get_varshaphal_saham
Read-onlyIdempotent

Calculate all 10 Tajika Saham (sensitive zodiac points) for a Varshaphal solar return chart using birth data and target year, revealing annual horoscope themes for specific life areas.

Instructions

Computes all 10 Tajika Saham (sensitive points) for a Varshaphal solar return chart. Sahams are the Tajika equivalent of Arabic Parts — mathematically derived zodiac points that focus the annual horoscope on specific life themes.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_varshaphal — understand the base solar return chart (year lord, Muntha, Varsha Ascendant) before interpreting Saham lords. The Saham is meaningless without knowing which house it occupies from the Varsha Ascendant. AFTER: asterwise_get_varshaphal_harsha_bala — assess the Saham lord's positional happiness score to determine ease or difficulty of manifestation.

INPUT CONTRACT: Same as asterwise_get_varshaphal — BirthData plus target_year. target_year (required int): The Gregorian calendar year of the solar return. Not age — the civil year (e.g. 2026). Feeding age instead of year silently produces the wrong return. time (required): Solar return Ascendant is time-sensitive. Accurate birth time is required for reliable Saham interpretation.

DO NOT CONFUSE WITH: asterwise_get_varshaphal — returns the full base solar return chart including Muntha, year lord, and planet positions; Saham points are not included there. asterwise_get_varshaphal_harsha_bala — scores planet positional happiness; this tool computes zodiac points, not planet positions. asterwise_get_gemstone_recommendations — birthchart gemstone recommendations, unrelated to Tajika Saham.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-varshaphal-saham/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesFour-digit calendar year, e.g. 2026. Defaults to the current year when omitted.
birthYesBirth data for a single person.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the read-only nature is covered. The description adds behavioral warnings about 'silently produces the wrong return' when year is actually age, and that accurate birth time is required for reliable Saham interpretation—useful context beyond 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.

Conciseness5/5

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

The description is well-structured with distinct sections (COMPUTES, BEFORE, AFTER, INPUT CONTRACT, DO NOT CONFUSE WITH, full docs link). Each section earns its place, and the repetition of warnings (e.g., year vs age) is purposeful reinforcement rather than fluff.

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

Completeness5/5

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

For a domain-specific Vedic astrology tool, the description provides sufficient workflow context (base chart needed first, Harsha Bala afterward) and points to a full output/error contract. It correctly assumes domain knowledge about Sahams while making the call flow clear.

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

Parameters5/5

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

Schema description coverage is 100%, and the prose enriches every key parameter: target_year is clarified as 'not age', birth.time explains the sunrise-chart fallback and explicitly warns never to pass '00:00' for unknown. These are critical semantic clarifications that go well beyond 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?

The description explicitly states the tool 'computes all 10 Tajika Saham (sensitive points) for a Varshaphal solar return chart', which is a specific verb on a specific resource. The DO NOT CONFUSE WITH section clearly distinguishes it from the base Varshaphal chart and Harsha Bala scoring.

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

Usage Guidelines5/5

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

The BEFORE/AFTER instructions tell the agent to first retrieve the base Varshaphal chart and later check Harsha Bala, while the DO NOT CONFUSE WITH section names three sibling tools and explains when not to use them. This gives explicit guidance on tool selection.

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/asterwise/asterwise-mcp'

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