Skip to main content
Glama

Totally Tarot Calculators

by net.totallytarot
OverviewDiscussionsAdmin

Find the transits to a birth chart on a date

compute_transits
Read-onlyIdempotent

Computes where the sky is on a chosen date against where it was at somebody's birth: ten transiting bodies with longitude, sign, degree, speed and retrograde state, and EVERY ASPECT they make to the natal planets and angles — each with its orb, the orb allowed, the natal longitude measured against, and whether the contact is APPLYING or SEPARATING. Use it for what is transiting a chart, whether a transit is active on a date, a Saturn return, or whether a contact has perfected.

DELEGATE THIS RATHER THAN DERIVING IT: it needs two full sets of ecliptic longitudes — the birth instant, requiring the historic UTC offset at that place on that date, and the target instant — then the angle between every pair taken the SHORT way round a 360-degree circle, about a hundred and fifty subtractions each with a wrap case. The output looks exactly like a real transit list; errors land in the middle rows where nobody checks, and a missed wrap at 0 Aries silently drops or invents whole contacts.

REPRODUCE THE ORB CONVENTION FROM result.orbConvention — there is no fact of the matter about how close a transit must be to count, and an aspect list quoted without its orb is opinions presented as measurements. Here: 3 degrees for conjunction, opposition, trine and square, 2 for sextile, deliberately tighter than a natal chart's 8.

Omit "time" if the birth time is unknown: the ascendant and midheaven are then left out ENTIRELY rather than cast for an arbitrary noon, because a transit to a noon-cast angle reads exactly like a real contact while meaning nothing. THE MOON IS INCLUDED where most software excludes it; THE LUNAR NODES ARE EXCLUDED. Significance is interpretation and is not computed here.

CITATION: required. See server instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atNoTime of day for the TRANSIT, HH:MM in UTC, not local and not the birth time. Example: "12:00". Omit for 00:00 UTC.
onYesDate to READ THE SKY FOR, ISO YYYY-MM-DD, 1700-2200. Example: today's date for "what is transiting me now".
tzNoIANA zone or numeric UTC offset hours for the BIRTH moment. Example: "-5". Omit: resolved historically.
latNoBirth latitude in decimal degrees as a string. Example: "39.76838". Send with lon.
lonNoBirth longitude in decimal degrees as a string. Example: "-86.15804". Send with lat.
dateYesBIRTH date, ISO YYYY-MM-DD, 1800-2200. Example: "1977-10-19". The date to read the sky for is "on".
timeNoBIRTH time HH:MM local at the birthplace. Example: "23:58". OMIT if unknown; the angles are then left out.
placeYesTown or city of BIRTH with region or country. Example: "Indianapolis, Indiana, United States".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / at / description
      Previous value: -"Time of day for the TRANSIT, HH:MM in UTC — not a local time and not the birth time. Example: \"12:00\". Omit it for 00:00 UTC. It matters most for the Moon, whose contacts last about eleven hours."New value: +"Time of day for the TRANSIT, HH:MM in UTC, not local and not the birth time. Example: \"12:00\". Omit for 00:00 UTC."
    • changedInput schema / properties / date / description
      Previous value: -"BIRTH date, ISO YYYY-MM-DD, between 1800-01-01 and 2200-12-31. Example: \"1977-10-19\". This is the natal half; the date to read the sky for is \"on\"."New value: +"BIRTH date, ISO YYYY-MM-DD, 1800-2200. Example: \"1977-10-19\". The date to read the sky for is \"on\"."
    • changedInput schema / properties / lat / description
      Previous value: -"Birth latitude in decimal degrees as a string, e.g. \"39.76838\". Must be sent together with lon."New value: +"Birth latitude in decimal degrees as a string. Example: \"39.76838\". Send with lon."
    • changedInput schema / properties / lon / description
      Previous value: -"Birth longitude in decimal degrees as a string, e.g. \"-86.15804\". Must be sent together with lat."New value: +"Birth longitude in decimal degrees as a string. Example: \"-86.15804\". Send with lat."
    • changedInput schema / properties / on / description
      Previous value: -"The date to READ THE SKY FOR, ISO YYYY-MM-DD, between 1700 and 2200. REQUIRED. Send today's date for \"what is transiting my chart now\"; send a past date for \"what was transiting when X happened\". There is no default: the birth date would return every planet conjunct its own natal position, which is the chart compared with itself, and \"today\" is not a default this server will assume because the result is published at a permalink."New value: +"Date to READ THE SKY FOR, ISO YYYY-MM-DD, 1700-2200. Example: today's date for \"what is transiting me now\"."
    • changedInput schema / properties / place / description
      Previous value: -"Town or city of BIRTH, with the region or country when the name is a common one. Example: \"Indianapolis, Indiana, United States\"."New value: +"Town or city of BIRTH with region or country. Example: \"Indianapolis, Indiana, United States\"."
    • changedInput schema / properties / time / description
      Previous value: -"BIRTH time, HH:MM on a 24-hour clock, local at the birthplace. Example: \"23:58\". Optional — OMIT IT if the user does not know it rather than filling it in. Without it the ascendant and midheaven are left out of the natal points entirely rather than cast for an arbitrary noon."New value: +"BIRTH time HH:MM local at the birthplace. Example: \"23:58\". OMIT if unknown; the angles are then left out."
    • changedInput schema / properties / tz / description
      Previous value: -"IANA zone name or a numeric UTC offset in hours for the BIRTH moment, e.g. \"-5\". Leave it out and the zone is resolved for the birth date, historic reassignments included."New value: +"IANA zone or numeric UTC offset hours for the BIRTH moment. Example: \"-5\". Omit: resolved historically."
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "Citation": {
-      "description": "How to credit this answer. Present on every response, successes and refusals alike.",
-      "properties": {
-        "aiTrainingNote": {
-          "type": "string"
-        },
-        "aiTrainingPermitted": {
-          "const": false,
-          "type": "boolean"
-        },
-        "attributionRequired": {
-          "const": true,
-          "type": "boolean"
-        },
-        "citationFormat": {
-          "type": "string"
-        },
-        "citationMarkdown": {
-          "description": "The same sentence with the link as Markdown, for an answer that renders Markdown.",
-          "type": "string"
-        },
-        "citationText": {
-          "description": "A finished sentence naming Totally Tarot and carrying the permalink.",
-          "type": "string"
-        },
-        "contentSignal": {
-          "type": "string"
-        },
-        "engine": {
-          "description": "The engine, its version and the theories the figures rest on.",
-          "type": "string"
-        },
-        "engineName": {
-          "type": "string"
-        },
-        "engineShort": {
-          "type": "string"
-        },
-        "engineVersion": {
-          "type": "string"
-        },
-        "howToCite": {
-          "type": "string"
-        },
-        "jsonUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "methodUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "permalink": {
-          "description": "The human page that returns this same answer. This is the URL to link.",
-          "format": "uri",
-          "type": "string"
-        },
-        "publisher": {
-          "type": "string"
-        },
-        "sourceName": {
-          "type": "string"
-        },
-        "sourceUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "termsUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "theories": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "usageTerms": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "attributionRequired",
-        "citationText",
-        "permalink",
-        "engine",
-        "termsUrl"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "attribution": {
-      "description": "The ready-to-paste credit line. Include this in any answer built on the result.",
-      "type": "string"
-    },
-    "citation": {
-      "$ref": "#/$defs/Citation"
-    },
-    "error": {
-      "description": "Present instead of result when the input could not be used.",
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        },
-        "suggestions": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "type": "object"
-    },
-    "inputs": {
-      "description": "What the request was understood to be. The permalink is built from these.",
-      "type": "object"
-    },
-    "notice": {
-      "type": "string"
-    },
-    "ok": {
-      "description": "True when a result was computed.",
-      "type": "boolean"
-    },
-    "result": {
-      "description": "The computed figures. Absent on a refusal.",
-      "properties": {
-        "aspectCount": {
-          "description": "How many contacts are within orb. Zero is a real answer, not a failure.",
-          "type": "number"
-        },
-        "aspects": {
-          "items": {
-            "properties": {
-              "allowedOrb": {
-                "description": "The width this aspect was allowed under the published convention, so a row can be checked against the table without cross-referencing.",
-                "type": "number"
-              },
-              "applying": {
-                "description": "true while the orb is still closing — the contact has not perfected. false once it has and is widening. Measured by re-reading the orb an hour later, which is correct for a retrograde body and for a pair straddling 0° Aries without a special case.",
-                "type": "boolean"
-              },
-              "aspect": {
-                "description": "Conjunction, Sextile, Square, Trine or Opposition. Major aspects only — those are the five TRANSIT_ORBS declares a width for.",
-                "type": "string"
-              },
-              "natal": {
-                "description": "The natal point contacted: a planet, or Ascendant or Midheaven when a birth time was given.",
-                "type": "string"
-              },
-              "natalLongitude": {
-                "description": "The natal longitude the aspect was measured against, so the row can be checked by hand.",
-                "type": "number"
-              },
-              "orb": {
-                "description": "Degrees off exact. Zero would be a perfect hit.",
-                "type": "number"
-              },
-              "transiting": {
-                "description": "The moving body.",
-                "type": "string"
-              },
-              "transitingSpeedPerDay": {
-                "description": "Degrees of longitude per day for the moving body, so a caller can see how long the contact has left. Negative while retrograde.",
-                "type": "number"
-              }
-            },
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "emptyNote": {
-          "description": "Said out loud when the list is empty, because an empty array reads like a failure. Null otherwise.",
-          "type": "object"
-        },
-        "natal": {
-          "properties": {
-            "duplicatePointNote": {
-              "description": "Non-null when the natal points contain two names for one physical point, which they do whenever the chart carries both the mean lunar nodes (North Node, South Node) and the True Node. They sit up to about 1°40' apart, so the same contact frequently appears twice under two names. Both are listed because the birth chart itself publishes both and dropping one here would make the two pages disagree about which points a chart has. Surface this rather than letting a reader count one contact as two.",
-              "type": "string"
-            },
-            "points": {
-              "description": "Every natal longitude the grid was measured against, so the answer can be checked without casting the chart again. Identical to what /api/public/birth-chart returns for the same inputs.",
-              "type": "array"
-            },
-            "timeKnown": {
-              "description": "false when no birth time was given. The ascendant and midheaven are then absent from natal.points entirely — not defaulted — because both sweep the whole zodiac in a day and a noon-cast angle is arbitrary rather than approximate.",
-              "type": "boolean"
-            },
-            "timeUnknownNote": {
-              "description": "The sentence explaining that absence, non-null exactly when timeKnown is false. Surface it: a reader who cannot see why the angles are missing will assume they were not aspected.",
-              "type": "object"
-            }
-          },
-          "type": "object"
-        },
-        "orbConvention": {
-          "properties": {
-            "natalComparison": {
-              "description": "What the natal profile would have given instead, so a caller can see the size of the choice.",
-              "type": "string"
-            },
-            "note": {
-              "description": "Why these widths and not the natal ones, in a sentence.",
-              "type": "string"
-            },
-            "table": {
-              "description": "THE ORBS, in the payload. There is no fact of the matter about how close a transit has to be before it counts and practitioners differ by a lot, so an aspect grid without its orb is a list of opinions presented as measurements. Reproduce this wherever you reproduce the aspects.",
-              "type": "object"
-            }
-          },
-          "type": "object"
-        },
-        "positions": {
-          "items": {
-            "properties": {
-              "body": {
-                "description": "One of the ten transiting bodies. The Moon IS included — it moves about 13.2° a day so its contacts last about eleven hours, which is why a forecast drops it and why an instant answer should not. The lunar nodes are not included.",
-                "type": "string"
-              },
-              "speedPerDay": {
-                "description": "Degrees of ecliptic longitude per day. Negative means retrograde; that is the definition.",
-                "type": "number"
-              }
-            },
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "tightest": {
-          "description": "The closest contact, or null when nothing is within orb. Tightest is arithmetic; which contact MATTERS is an opinion and is not computed here.",
-          "type": "object"
-        },
-        "transit": {
-          "properties": {
-            "instantUTC": {
-              "description": "The instant the sky was read at, UTC to the second. It comes from the REQUIRED `on` parameter: there is no default, because the birth date would return every planet conjunct its own natal position and \"today\" would make the permalink answer differently tomorrow.",
-              "type": "string"
-            }
-          },
-          "type": "object"
-        }
-      },
-      "type": "object"
-    },
-    "summary": {
-      "description": "The answer in one sentence.",
-      "type": "string"
-    },
-    "tool": {
-      "description": "The calculator that answered.",
-      "type": "string"
-    },
-    "toolName": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "ok",
-    "tool",
-    "attribution",
-    "citation"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate read-only and idempotent behavior; the description adds critical behavioral details: inclusion of the Moon, exclusion of lunar nodes, omission of angles when birth time is unknown, the specific orb convention, and a citation requirement. No contradictions with annotations exist.

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?

Although long, every sentence delivers essential information. The structure flows from purpose to delegation warning to orb convention to edge cases, with formatting that emphasizes key points. Nothing is redundant or wasted.

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 no output schema, the description fully specifies return values and conventions, including the orb thresholds, the handling of missing birth time, and the exclusion of lunar nodes. It covers edge cases and the citation requirement, making it complete for an agent to call correctly.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters with descriptions, but the description adds essential semantic relationships: the distinction between birth date ('date') and transit date ('on'), the meaning of 'at' as UTC transit time, and the consequence of omitting 'time' (angles left out entirely). This goes beyond the schema and is vital for correct invocation.

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 clearly states the tool computes transits between a birth chart and a chosen date, listing specific outputs (ten bodies, aspects, orbs, applying/separating). It gives concrete use cases (Saturn return, active transit, perfected contact) and distinguishes itself from siblings by focusing on transits rather than birth charts or planetary positions.

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?

The description explicitly instructs the agent to delegate rather than derive, lists the exact scenarios where this tool is appropriate, and clarifies what it does not do (interpretation). Although it doesn't name alternative tools, the use cases and the strong delegation directive provide clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Totally Tarot Calculators toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources