Asterwise

Western Daily Factors

asterwise_get_western_daily_factors

Read-onlyIdempotent

Every Western factor for one person on one day, in one shape, with no weighting. Each factor carries its raw value and range, its frame, the verdict Lilly's rules give, the rule's source, signification ids, the time it holds and whether it depends on the birth time.

WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: asterwise_get_western_events — the same over a range, as a timeline.

INPUT CONTRACT: birth — WesternBirthData (house_system used for natal_house). target_date (optional YYYY-MM-DD; defaults to today in the birth timezone). target_time (optional HH:MM; defaults to 12:00) — the local time in target_timezone the day's sky is read. target_timezone (optional IANA).

DO NOT CONFUSE WITH: asterwise_get_western_transits_daily — the aspects only, with no rules. asterwise_get_western_horoscope — AI-written sun-sign text.

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

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": "asterwise_get_western_daily_factors"
  }
}

Input Schema

Name	Required	Description	Default
`birth`	Yes	Birth data for Western astrology tools (tropical zodiac).
`target_date`	No	Day to read, YYYY-MM-DD. Defaults to today in the birth timezone.
`target_time`	No	Local time HH:MM (24-hour) in target_timezone on the day at which the sky is read. Defaults to 12:00. Pass the user's own time so the Moon is where the user sees it.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown
`target_timezone`	No	IANA timezone of the day. 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 28, 2026

changedInput schema / properties / target_time / anyOf

Previous value: -[
-  {
-    "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / target_time / description

Previous value: -"Local time HH:MM (24-hour) on the day at which the sky is read. Defaults to 12:00. Pass the user's own time so the Moon is where the user sees it."New value: +"Local time HH:MM (24-hour) in target_timezone on the day at which the sky is read. Defaults to 12:00. Pass the user's own time so the Moon is where the user sees it."

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / target_time

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Local time HH:MM (24-hour) on the day at which the sky is read. Defaults to 12:00. Pass the user's own time so the Moon is where the user sees it."
+}

AddedOct 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds substantial behavioral context beyond that: no weighting, each factor's raw value and range, frame, Lilly rule verdict and source, signification ids, holding time, and birth-time dependence.

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 front-loaded with the core purpose, then organized into workflow, input contract, and sibling disambiguation. The sections are dense but each one carries actionable information.

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?

For a complex astrology tool with nested birth data and multiple optional timing parameters, the description covers purpose, output shape, prerequisites, follow-up tools, sibling exclusions, and input defaults. An output schema and full annotations also exist, so no critical context is missing.

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 adds useful semantics, especially that birth.house_system is used for natal_house and how target_time and target_timezone define the local sky-reading moment, though it does not add much beyond the schema for every parameter.

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 opening sentence states a specific scope: every Western factor for one person on one day, with no weighting. It also distinguishes the tool from siblings through dedicated workflow and 'DO NOT CONFUSE WITH' sections, so an agent can identify it without opening the 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?

Usage is explicit: run asterwise_get_western_natal before this tool, use asterwise_get_western_events afterward for ranges, and avoid asterwise_get_western_transits_daily and asterwise_get_western_horoscope. These are concrete when-to-use and when-not-to-use instructions.

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?