Skip to main content
Glama

Your transits

get_personal_transits
Read-only

Lists dated transits to one person's birth chart: when the moving planets make exact aspects to the natal planets, and to the rising degree and Midheaven when the birth time and place are known, each with what astrology traditionally reads into it and a "Reading confidence NN%" label that says how specific the details were, not the odds of an event. By default it covers the next 30 days. In year-ahead mode it gives the year's highlights: the slow planets on the personal planets, the solar return, a Saturn return, Jupiter and Saturn changing sign, and eclipses near natal planets. It fits "my transits", "what is coming up for me" or "my year ahead", once a birth date has been given; get_horoscope and get_horoscope_period hold the Sun-sign horoscopes. A window is at most 366 days, and a window over 92 days keeps to Jupiter through Pluto. The window cannot start before the birth date. Without a birth time the Moon, the rising degree and the Midheaven are left out. Without currentZone dates use the birthplace's clock, or UTC if that is missing too, and the answer says which. Each line is astrology's reading, not a guarantee, and not health, financial or medical advice. It refuses a birth date less than 13 years ago, so it also refuses transits to a chart of today. For a birth date under 18 romantic and attraction readings are left out and a note says so.

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

Input Schema

NameRequiredDescriptionDefault
toNoFor window: the last day, at most 366 days after from. Defaults to a 30-day window, from included.
fromNoFor window: the first day, such as 2026-11-01. Defaults to today.
modeNowindow (the default): every exact contact between from and to. year-ahead: the year from today, with Jupiter and Saturn, the solar return, a Saturn return, sign changes and eclipses near the chart.
timeNoThe birth time on the local clock, only if the person knows it. Never guess it. Needs zone. Without it the Moon, rising degree and Midheaven are left out.
zoneNoThe birthplace's time zone, such as Europe/Madrid. Needed with a time or a place.
latitudeNoOptional. The birthplace's latitude; with a birth time it adds the rising degree and Midheaven. Give it with longitude and zone. Nothing is stored.
birthDateYesThe birth date, such as 1990-05-03 (years 1800 to 2199).
longitudeNoOptional. The birthplace's longitude, with latitude. Nothing is stored.
currentZoneNoWhere the person lives now, such as Asia/Bangkok, so dates fall on their own clock. Without it, dates use the birthplace clock, or UTC if that is missing too, and the answer says which.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare a read-only, non-destructive, closed-world call, and the description adds substantial context beyond that: the 366-day window cap, the Jupiter-through-Pluto restriction past 92 days, the no-start-before-birth-date rule, the 13-year refusal, omission of Moon/rising/Midheaven without a birth time, and the under-18 suppression of romantic readings. It even explains what the "Reading confidence NN%" label means and disclaims health/financial advice, which the annotations cannot express. Note it does not address the idempotentHint=false annotation on what is a deterministic read.

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?

Front-loaded with what the tool returns before the usage and constraint details, and nearly every sentence adds a distinct rule. It is a dense block of prose with some clauses that read as legal boilerplate (the advice disclaimer), which keeps it short of a 5.

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?

For a nine-parameter tool with an output schema already covering return values, the description supplies everything else an agent needs: defaults, hard limits, degradation without birth time, refusal conditions, and timezone resolution. Nothing material about invocation is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds rules the schema does not carry: the default 30-day window, the 366-day maximum, the 92-day slow-planet trimming, and the timezone fallback chain for currentZone (birthplace clock, then UTC, with the answer disclosing which). The dependent relationship between time and zone, and latitude/longitude only mattering with both, is reinforced rather than merely restated.

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?

Opens with a specific verb and resource: "Lists dated transits to one person's birth chart", then spells out exactly what a transit line contains (exact aspects, rising degree, Midheaven, a reading). It contrasts itself against get_horoscope and get_horoscope_period by naming what those hold instead, so an agent can separate the tools without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete user phrasings this fits ("my transits", "what is coming up for me", "my year ahead") plus the precondition that a birth date must already be given, and explicitly routes Sun-sign horoscope requests to get_horoscope/get_horoscope_period. It also states hard exclusions (birth date under 13 years ago is refused) and the mode split between window and year-ahead.

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.