Skip to main content
Glama

AstroLogics

Upcoming planetary transits

get_transit_calendar
Read-onlyIdempotent

List upcoming planetary transit events (sign changes, retrograde and direct stations, eclipses) from today for up to 180 days, plus the grahas retrograde right now.

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_transit_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to cover. Defaults to 90.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.

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.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and non-open-world behavior, so the safety profile is covered. The description adds real value beyond them: the forward-only window starting today, the 180-day ceiling, and the fact that a current-retrograde snapshot is bundled in — an agent would not infer that from the structured fields.

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?

A single front-loaded sentence with the resource first, the event types enumerated in parentheses, and the scope limits after. No filler and nothing that could be trimmed without losing information.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so by naming the event categories plus the current-retrograde list. It is adequate for a two-optional-parameter read tool; only the shape of individual event entries is left unspecified.

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 coverage is 100%, with both 'days' (default 90, max 180) and the 'language' enum fully documented in the schema. The description only restates the 180-day ceiling and says nothing about the language parameter or the default, so it adds little beyond the schema — baseline 3.

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?

States a specific verb ('List') and resource ('upcoming planetary transit events') and enumerates the event types covered: sign changes, retrograde/direct stations, eclipses. It also names the bonus payload (grahas retrograde right now) and the 180-day horizon, which lets an agent separate it from position-lookup or panchang siblings.

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?

The temporal scope is explicit ('from today for up to 180 days') and the inclusion of currently-retrograde grahas clarifies the boundary case an agent might otherwise query separately. It does not name an alternative tool or state when-not to use it, so it stops short of a 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