Skip to main content
Glama

Supastro

See today's transits for a birth chart

get_personal_transits
Read-onlyIdempotent

Calculates where each of the nine planets is today for one birth chart: its sign, its house counted from the rising sign, its house counted from the birth Moon, and the Moon-sign transit result for that house under the classical rule (good, blocked by vedha, eased or hard). Use it when someone asks what is transiting their chart now, which house a planet is passing through for them, or how the current transits sit for their Moon sign. Returns computed placements and the rule's result for each. Covers this moment by default, or another 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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "get_personal_transits"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. The day to check as YYYY-MM-DD, read at 12:00 UTC. Defaults to this moment. Convert the person's own wording to this form; if an all-number date could be read two ways, ask which number is the day.
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the house systems used (from rising sign and from birth Moon), the classical vedha-based verdict categories, the default of 'this moment', and that results are computed per planet. It does not discuss date interpretation edge cases or precision limits, though the schema covers the date-format caveats.

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 the core computation, then use cases, then return and date scope. Three sentences, each carrying information, with the enumerated house conventions being the densest but still purposeful. Minor redundancy between the opening list of outputs and the later 'Returns computed placements' sentence.

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 six parameters and no output schema, the description carries the return-value burden and does so at a high level ('computed placements and the rule's result for each'). Required inputs, coordinate fallbacks, and date defaults are all covered by the schema. What is missing is how the Moon-sign verdict categories are chosen or how many placements to expect, but for a read-only lookup this is close to complete.

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% and each parameter carries detailed guidance (date format, the two-ways-to-read-a-date ambiguity, latitude/longitude pairing, birth time AM/PM ambiguity). The description adds only the date default ('this moment, or another date'), which the schema already states. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource: calculates the nine planets' positions today for one birth chart, and enumerates what each placement includes (sign, house from rising sign, house from birth Moon, Moon-sign transit rule result). That is far more specific than the title alone. It stops short of naming a sibling such as get_major_transits, so the agent must infer the boundary between 'today's transits' and 'major transits' on its own.

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?

Gives three concrete triggering questions (what is transiting their chart now, which house a planet is passing through, how current transits sit for their Moon sign), which is strong when-to-use guidance. It also clarifies the default date scope and that another date can be supplied. It offers no when-not-to-use guidance or named alternative for longer-range or non-Moon-sign transit work.

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