Skip to main content
Glama

Life milestones

get_life_milestones
Read-only

Lists astrology's life milestones from a birth date: each Jupiter return (about every 12 years), the Saturn returns (around 29, 58 and 88) and the Uranus opposition (early forties), with dates, ages and every pass of a retrograde loop, the next one coming, and counts of the full Moons and Mercury retrogrades since birth. It fits a question about a Saturn return or another lifetime return, from a known birth date. It makes no prediction. A birth date is enough; a birth time needs the birthplace's time zone. It refuses a birth date less than 13 years ago. Its share link shows the milestone and the age at it, never the birth date.

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": {
      "birthDate": "<birthDate>"
    },
    "name": "get_life_milestones"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoThe birth time on the local clock, if known. Needs zone.
zoneNoThe birthplace's time zone, such as Europe/London. Needed with a time.
birthDateYesThe birth date, such as 1997-03-15.
longitudeNoThe birthplace's longitude, if known, for birth times before standard time.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already cover read-only and closed-world safety, and the description adds real behavior beyond them: refusal of recent birth dates, the no-prediction stance, inclusion of every retrograde loop pass with the next one coming, and the privacy detail that a share link never exposes the birth date. Only minor gaps remain, such as whether repeated calls yield identical output (idempotentHint is false but the variability is unexplained).

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?

It is a compact, front-loaded block where each sentence carries distinct information: payload contents, use case, non-prediction scope, parameter dependency, refusal guard, and share-link privacy. No sentence restates the name or the structured fields.

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?

With an output schema already present, the description need not explain return values, yet it still sketches what a result contains (dates, ages, pass counts). Given four parameters with full schema coverage and annotations covering safety, an agent has everything needed to decide and call correctly.

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%, so the baseline is 3 and the schema already documents all four parameters including the time/zone dependency. The description reinforces that a birth date alone suffices and that a time requires the birthplace's time zone, but adds no syntax or format detail beyond the schema.

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 ('Lists astrology's life milestones from a birth date') and then enumerates the exact contents: Jupiter returns, Saturn returns at ~29/58/88, Uranus opposition, plus counts of full Moons and Mercury retrogrades. That level of specificity clearly separates it from siblings like get_natal_chart or get_personal_transits 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 Guidelines4/5

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

It states the triggering question type ('a question about a Saturn return or another lifetime return, from a known birth date') and an explicit exclusion ('It makes no prediction'), plus a hard refusal condition (birth date less than 13 years ago). It stops short of naming a specific alternative sibling when the user wants a natal chart or current transits, so the routing guidance is clear but not exhaustive.

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.