Skip to main content
Glama
Dinesh-Gahlot

mcp-indian-astrology

divine_get_sub_planet_chart

Read-onlyIdempotent

Generate a sub-planet (Upagraha) chart as an SVG or image for Vedic astrology, showing placements in North or South Indian style using birth details.

Instructions

Generate a sub-planet (Upagraha) chart as SVG and image.

Returns a visual chart showing the placement of sub-planets (Dhuma, Vyatipata, Parivesha, etc.) in North or South Indian style.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesBirth day (e.g., '24')
lanNoLanguage codeen
latYesLatitude (e.g., '28.7041')
lonYesLongitude (e.g., '77.1025')
minYesBirth minute (e.g., '40')
secNoBirth second0
hourYesBirth hour in 24h format (e.g., '14')
yearYesBirth year (e.g., '1990')
monthYesBirth month (e.g., '05')
placeYesBirth place (e.g., 'New Delhi')
tzoneYesTimezone offset (e.g., '5.5')
genderYesGender: 'male' or 'female'
full_nameYesFull name of the person
chart_typeNoChart style: 'north' (diamond) or 'south' (square)north
line_colorNoChart line color as hex (e.g., '#333333')
sign_colorNoSign label color as hex (e.g., '#333333')
chart_colorNoChart background color as hex (e.g., '#ffffff')
planet_colorNoPlanet label color as hex (e.g., '#333333')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that the tool returns a visual chart as SVG and image, which is useful context beyond annotations. No contradiction, but no further behavioral traits (e.g., rate limits, auth) are disclosed.

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?

Two succinct sentences with no fluff. The main purpose is front-loaded, and the example sub-planets and chart styles are concisely included. Every sentence earns its place.

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

Completeness4/5

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

Despite having 18 parameters and 11 required ones, the description is sufficient because the schema provides full parameter documentation and an output schema exists. It clearly states the output format (SVG and image) and content (sub-planet placement). Missing usage guidance is a small gap, but the core operational details are present.

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 description coverage is 100%, so the baseline is 3. The description adds minimal parameter meaning beyond the schema, only mentioning North/South Indian style which maps to the chart_type parameter. It does not explain any of the other 18 parameters beyond what the schema already provides.

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?

Description states a specific verb ('Generate') and resource ('sub-planet (Upagraha) chart as SVG and image'), explicitly naming example sub-planets (Dhuma, Vyatipata, Parivesha) and chart styles (North/South Indian). This clearly sets it apart from siblings like divine_get_sub_planet_positions or general horoscope chart tools.

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 on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or how it differs from related tools such as divine_get_sub_planet_positions. Usage is only implied by the description.

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