Skip to main content
Glama

Cosmic Chemistry

Saturn return dates

saturn_return_dates
Read-onlyIdempotent

Use this when someone asks when their Saturn return is (in Vedic, sidereal reckoning), whether they are in it now, or at what ages it comes. Also use for "Saturn return at 28/29" and Shani return. Returns every Saturn return with dates and ages. Needs birth date and town (a past birth: it counts from today); ask if missing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "birth_date": "<birth_date>",
      "birth_place": "<birth_place>"
    },
    "name": "saturn_return_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
birth_dateYesDate of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_timeNoLocal clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_placeYesTown or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 behavior, so the safety profile is covered. The description adds useful behavioral context: the calculation uses Vedic sidereal reckoning, returns every Saturn return with dates and ages, and instructs the agent to ask for missing birth data. It leaves the optional birth_time's effect on accuracy unexplained, but the added context is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with usage triggers, then states the return values, then notes required inputs. It is appropriately sized and mostly free of waste, though the parenthetical 'a past birth: it counts from today' is cryptic and slightly interrupts flow.

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 explaining return values; it does so by saying it returns every Saturn return with dates and ages. It also tells the agent to ask for missing birth data, which is important for a required-parameter tool. The only minor gap is not clarifying how birth_time affects precision.

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 schema already documents all three parameters. The description reinforces that birth date and town are required and says to ask if missing, but adds little semantic detail beyond the schema; the phrase 'a past birth: it counts from today' is ambiguous and the optional birth_time is not discussed.

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 states a specific verb and resource: it returns every Saturn return with dates and ages. It further distinguishes the calculation as Vedic/sidereal and mentions the Shani return alias, so an agent can tell it apart from general birth-chart or retrograde tools. The purpose is unmistakable.

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 description gives explicit when-to-use guidance: when someone asks when their Saturn return is, whether they are in it now, or at what ages it comes, plus the 'Saturn return at 28/29' and Shani return phrasings. It does not name when not to use it or point to an alternative sibling, but for a specialized query this is strong routing guidance.

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