Skip to main content
Glama

NatalChart.AI Astrology

Transits for a period

transits
Read-onlyIdempotent

Up to 60 transit events in a window of up to 92 days, the most significant kept when there are more: exact transit-to-natal aspects by date, sign ingresses and stations. (Premium or MAX) Use it for forecasts over weeks or months (a year is four windows); for a single day use daily_transits.

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": "<birth>"
    },
    "name": "transits"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoAt most 92 days after from; 30 days by default.
fromNo
birthYes

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 the safety profile (readOnly, idempotent, closed-world), yet the description still adds substantive behavior: the 60-event cap and the 'most significant kept' selection rule, which tells the agent results can be silently truncated. It does not say whether a truncated response is flagged or how results are ordered, which keeps this just short of the top score.

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?

Two tight sentences, with the substantive facts (return contents, cap, window limit, tier gate) front-loaded before the usage routing. The opening is a verbless fragment, which makes it slightly telegraphic, but no sentence is wasted.

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?

For a nested-birth-object tool with no output schema, the description does enough: it enumerates the event kinds returned and the window/volume limits, and pairs with annotations on safety. The missing piece is response shape beyond the event categories and whether truncation is signaled.

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 only 33%, so the description must compensate, and it does so partially: the '92 days' and 'a year is four windows' framing clarifies window sizing and pairs with the documented 'to' constraint. The 'from' parameter is undocumented in both places, and nothing is said about how the nested birth object is validated beyond what the schema already states.

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?

Names the concrete resource (transit events: exact transit-to-natal aspects by date, sign ingresses, stations) with scope and volume caps. It also explicitly differentiates itself from the sibling daily_transits, so an agent can route between the two 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?

States exactly when to use it (forecasts over weeks or months, with 'a year is four windows' quantifying the workload) and names the alternative for the other case ('for a single day use daily_transits'). The eligibility condition (Premium or MAX) is also disclosed up front.

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