Skip to main content
Glama

AstroLogics

Planet positions at a moment

get_planet_positions
Read-onlyIdempotent

Get the sidereal (Lahiri) positions of the nine grahas and the ascendant for any date, time and place: sign, degree, nakshatra, pada and retrograde state. Defaults to now in New Delhi when date, time or place are omitted.

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
dateNoDate, YYYY-MM-DD. Defaults to today (IST).
timeNoLocal time, HH:MM. Defaults to now.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeNoLatitude in decimal degrees. Omit with longitude for New Delhi.
longitudeNoLongitude in decimal degrees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the ayanamsa convention (Lahiri sidereal, which matters versus tropical results) and the defaulting behavior for date, time and place. It does not discuss precision, timezone interpretation, or result size, which keeps it from a 5.

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 sentences, front-loaded with the what and the output shape, followed by the default behavior. No filler, no restatement of the title.

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?

With no output schema, the description does the necessary work by naming the returned fields and the zodiac system used. What remains unstated is minor for a read-only lookup: timezone interpretation of the time argument and any precision guarantees, both of which the schema partially covers.

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 each parameter is already documented, including the New Delhi fallback and the en/hi language enum. The description only consolidates those defaults into one sentence rather than adding format or semantic detail beyond the schema, so the baseline 3 applies.

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?

Specific verb plus resource: returns sidereal (Lahiri) positions of the nine grahas and the ascendant, and it enumerates exactly what is returned (sign, degree, nakshatra, pada, retrograde state). The scope phrase 'for any date, time and place' plus 'defaults to now' separates it from natal-chart siblings like get_birth_chart without needing to name them.

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?

Usage is implied rather than stated: it is for arbitrary moments, and omitting date/time/place yields the current sky in New Delhi. There is no explicit when-to-use/when-not guidance and no named alternative for natal or transit-calendar queries, so an agent must infer the boundary itself.

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