Asterwise

Western Weekly Transits

asterwise_get_western_transits_weekly

Read-onlyIdempotent

7-day transit window vs natal chart. Returns day-by-day transit snapshots plus peak aspects (active 4+ days in the window). Use start_date to set the week start; defaults to today.

WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: asterwise_get_western_transits_monthly — for full month.

INPUT CONTRACT: birth — WesternBirthData. house_system picks the natal houses used for natal_house on each transiting planet (default placidus). start_date (optional YYYY-MM-DD) — week start; defaults to today. snapshot_time (optional HH:MM) and snapshot_timezone (IANA) read each day's sky at that local clock time instead of 12:00 UTC.

DO NOT CONFUSE WITH: asterwise_get_western_transits_daily — single day. asterwise_get_western_transits_monthly — 30 days vs 7.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-transits-weekly/

Input Schema

Name	Required	Description	Default
`birth`	Yes	Birth data for Western astrology tools (tropical zodiac).
`start_date`	No	First day of the 7-day window, YYYY-MM-DD. Defaults to today (UTC).
`snapshot_time`	No	Local clock time HH:MM at which each day's sky is read. Default 12:00 UTC.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown
`snapshot_timezone`	No	IANA timezone for snapshot_time. Defaults to the birth timezone.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / snapshot_time

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{2}:\\d{2}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Local clock time HH:MM at which each day's sky is read. Default 12:00 UTC."
+}

addedInput schema / properties / snapshot_timezone

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "IANA timezone for snapshot_time. Defaults to the birth timezone."
+}

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / start_date / description

Previous value: -"Start of the window, YYYY-MM-DD. Defaults to today when omitted."New value: +"First day of the 7-day window, YYYY-MM-DD. Defaults to today (UTC)."

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

addedInput schema / properties / start_date / description

Added value: +"Start of the window, YYYY-MM-DD. Defaults to today when omitted."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "birth",
-  "response_format"
-]New value: +[
+  "birth"
+]
```
AddedMay 1, 2026

TDQS

A4.6/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 real behavioral context beyond that: the definition of 'peak aspects' (active 4+ days), the default week start of today, and how snapshot_time/snapshot_timezone resolve the daily sky-reading clock. It defers error behavior to a docs link, which is acceptable but a small gap.

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 one-sentence summary followed by clearly labeled WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE sections — easy to scan. A few schema details (YYYY-MM-DD, defaults) are restated, so it is slightly redundant rather than maximally tight.

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 an output schema present, return values need no explanation. The description supplies everything else an agent needs: workflow prerequisites, alternative disambiguation, the input contract including house-system and snapshot-time interactions, and a link to the full output/error contract.

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. The description still adds meaning beyond the schema: that house_system controls the natal houses used for natal_house on each transiting planet, and that snapshot_time/snapshot_timezone re-read each day's sky at a chosen local clock time rather than the default 12:00 UTC. It does not cover response_format or person_name, keeping it from a 5.

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?

States a specific verb and resource (7-day transit window vs natal chart) plus the exact payload shape: day-by-day snapshots plus peak aspects defined as active 4+ days. This cleanly distinguishes it from the daily and monthly siblings without needing to open 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 explicit workflow ordering (BEFORE natal, AFTER monthly) and an explicit 'DO NOT CONFUSE WITH' block naming both alternatives with their differing windows (single day vs 7 vs 30 days). No inference required to pick the right tool.

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

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?