Skip to main content
Glama

Supastro

Get current planet positions

get_planet_positions
Read-onlyIdempotent

Calculates where the nine Vedic planets are right now in the sidereal zodiac (Lahiri): each planet's sign, degree, nakshatra and pada, whether it is retrograde, and when it next changes sign. Use it when someone asks where a planet is today, which planets are retrograde, or when a planet changes sign. Needs no birth details. Returns positions and dates only, with no interpretation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_planet_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_zoneNoOptional. IANA time zone for the dates shown, for example "Asia/Kolkata". Defaults to UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation, so the description does not need to restate those safety properties. It adds useful behavioral context by saying no birth details are required and that the output is limited to positions and dates with no interpretation. That is strong disclosure, though it does not discuss edge cases such as time-zone handling.

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 three tight sentences with no wasted wording. It front-loads the core calculation and returned fields, then provides usage triggers, then closes with scope limitations. Each sentence contributes distinct information.

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 a tool with one fully documented optional parameter, no output schema, and annotations that already cover safety behavior, the description is complete. It explains what is returned and explicitly rules out interpretation, so an agent can call it confidently without additional context.

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?

The single optional time_zone parameter is fully documented in the schema with an IANA format example and UTC default, so the baseline is 3. The description does not add any parameter-level detail beyond what the schema already provides, but no compensation is needed because schema coverage is complete.

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: calculates the current positions of the nine Vedic planets in the sidereal zodiac using Lahiri ayanamsa. It then enumerates the returned fields (sign, degree, nakshatra, pada, retrogradeness, next sign change), making the tool's purpose unambiguous and clearly distinct from birth-chart or transit tools.

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

Usage Guidelines4/5

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

It gives clear usage triggers: when someone asks where a planet is today, which planets are retrograde, or when a planet changes sign. It also clarifies that no birth details are needed, which helps separate it from personalized tools. It stops short of naming explicit alternatives or when-not-to-use cases, so it is not a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources