Skip to main content
Glama

Asterwise

by com.asterwise.mcp

Planet Nature

asterwise_get_planet_nature
Read-onlyIdempotent

Returns classical graha (planet) properties for all nine planets or a single planet per classical Vedic tradition.

WORKFLOW: BEFORE: None — standalone reference. AFTER: asterwise_get_puja_suggestions — propitiation for a specific graha.

INPUT CONTRACT: planet (optional): One of Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Omit to get all nine planets.

DO NOT CONFUSE WITH: asterwise_get_puja_suggestions — ritual propitiation per planet, not properties. asterwise_get_rudraksha — bead recommendations per planet, not natal properties.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planetNoPlanet name in English, e.g. 'Jupiter', 'Saturn', 'Rahu'.
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. Changed2 schema fields changed
    • addedInput schema / properties / planet / description
      Added value: +"Planet name in English, e.g. 'Jupiter', 'Saturn', 'Rahu'."
    • addedInput schema / properties / response_format / description
      Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."
  2. Changed2 schema fields changed
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • removedInput schema / required
      Removed value: -[
-  "response_format"
-]
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: the tool is a standalone reference, supports omitting the planet for all nine, and provides an output/error handling contract link.

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-organized under clear headings (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) and front-loads the core purpose in the first sentence. Every section earns its place, and the formatting makes it easy for an agent to scan and extract the important constraints.

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?

Given the output schema is present, the description does not need to explain return values. It covers optional behavior, format selection, workflow dependencies, sibling distinctions, and points to a full contract link, making the tool adequately specified for correct invocation.

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

Parameters4/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 meaningful value by enumerating valid planet values, clarifying that omitting the planet returns all nine, and reinforcing the response_format behavior in the INPUT CONTRACT.

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 opens with a specific verb and resource: 'Returns classical graha (planet) properties for all nine planets or a single planet per classical Vedic tradition.' It also explicitly distinguishes itself from asterwise_get_puja_suggestions and asterwise_get_rudraksha in the 'DO NOT CONFUSE WITH' section, making it easy to differentiate from siblings.

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 WORKFLOW section states there is no prerequisite and names the logical next step (asterwise_get_puja_suggestions) for propitiation. The 'DO NOT CONFUSE WITH' section explicitly calls out alternatives and clarifies that they serve different purposes, giving the agent clear routing guidance.

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

All Asterwise toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Many tools are well-differentiated by explicit 'DO NOT CONFUSE WITH' notes, but the sheer number of near-neighbor pairs (e.g., crystal vs gemstone recommendations, natal chart variants, dasha systems, compatibility systems, tarot draw variants) creates real selection risk. The descriptions mitigate overlap, but an agent browsing 103 tools will struggle to pick the right one.

Naming Consistency5/5

Every tool follows the asterwise_get_* or asterwise_draw_* prefix convention with a clear noun phrase (e.g., asterwise_get_natal_chart, asterwise_draw_tarot_cards). The two verbs 'get' and 'draw' are semantically appropriate, and there are no camelCase or mixed-style names.

Tool Count1/5

103 tools is far beyond a manageable MCP surface. While the domain is broad (Vedic astrology, Western astrology, numerology, tarot, crystals, dream symbols), the server bundles multiple distinct domains into one namespace, making it nearly impossible for an agent to discover the right tool efficiently.

Completeness4/5

The surface is impressively comprehensive across astrology, numerology, tarot, and remedies, with deep coverage of dasha systems, compatibility frameworks, and chart types. Minor gaps exist (e.g., no tarot interpretation endpoint, no batch operations, no update/delete since it's read-only data), but for a reference/prediction API the coverage is strong.

Resources