Skip to main content
Glama

Transits to a birth chart

transits
Read-onlyIdempotent

Every exact transit of the planets (Sun to Pluto; the Moon is left out as it aspects everything monthly) to a birth chart's planets, Ascendant and Midheaven over a span, with the exact date of each and whether the planet is retrograde. Major aspects: conjunction, sextile, square, trine, opposition.

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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezone": "<timezone>"
    },
    "name": "transits"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD
daysNoLength of the span in days (default 30, at most 366)
fromNoStart date (default today)
timeNoLocal clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable.
placeNoBirthplace name, echoed back so the user can check the coordinates
latitudeYesBirthplace latitude in decimal degrees (north positive)
timezoneYesIANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it.
longitudeYesBirthplace longitude in decimal degrees (east positive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: it excludes the Moon and explains why, lists the major aspects, and says each result includes the exact date and retrograde status.

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?

The description is a single compact sentence that front-loads the core operation and parenthetically explains the Moon exclusion. It is dense with relevant information and has no wasted clauses.

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?

With no output schema, the description carries the burden of explaining return content, and it does so by naming exact dates, retrograde status, and included aspects. It is nearly complete for invocation, with the main gap being no sibling-tool routing guidance.

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 all eight parameters are documented in the schema itself. The description adds only a high-level reference to the birth chart and span, not syntax or format details beyond what the schema already provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific astrological operation: exact planetary transits to a birth chart's planets, Ascendant, and Midheaven over a span. It is clear what the tool computes, though it does not explicitly distinguish itself from siblings such as progressions, returns, or synastry.

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

Usage Guidelines2/5

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

The description implies usage by describing transit calculations, but it gives no explicit guidance on when to choose this tool over siblings like progressions, returns, synastry, or natal_chart. There are no when-not conditions or named alternatives.

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