Skip to main content
Glama
Sign In

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

Western Solar Arc

asterwise_get_western_solar_arc
Read-onlyIdempotent

Western Solar Arc Directions for a target date: the solar arc (progressed Sun minus natal Sun) is added to every natal planet and angle. It is approximately 1° per year; unlike secondary progressions, all planets advance at the same rate.

WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: None.

INPUT CONTRACT: birth — WesternBirthData. target_date (optional YYYY-MM-DD) — defaults to today.

DO NOT CONFUSE WITH: asterwise_get_western_secondary_progressions — each planet moves at its own rate. asterwise_get_western_transits_daily — real-time transits, not arc directions.

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

Input Schema

NameRequiredDescriptionDefault
birthYesBirth data for Western astrology tools (tropical zodiac).
target_dateNoDate to direct the chart to, YYYY-MM-DD. Defaults to today (UTC).
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target_date / description
      Previous value: -"Date in YYYY-MM-DD format. Defaults to today when omitted."New value: +"Date to direct the chart to, YYYY-MM-DD. Defaults to today (UTC)."
  2. Changed2 schema fields changed
    • 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 / target_date / description
      Added value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."
  3. Changed2 schema fields changed
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • changedInput schema / required
      Previous value: -[
-  "birth",
-  "response_format"
-]New value: +[
+  "birth"
+]
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read. Beyond that, the description adds domain behavior (~1° per year, uniform advancement across all planets) and notes target_date defaults to today, which helps the agent reason about output. It stops short of describing output structure, though the output schema covers that.

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?

Front-loaded core definition followed by labeled WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE sections. Every line is scannable and none is redundant.

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 annotations covering safety, a rich nested input schema, and an output schema existent (so returns need not be described), the description supplies the remaining needs: prerequisite ordering, sibling disambiguation, and a docs link for the full output/error contract.

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 nested birth fields are fully documented, so the schema carries the parameter burden. The description only restates the target_date default, adding no date handling detail beyond the schema. Baseline 3 applies.

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 description states a specific technique (solar arc directions) and precisely defines it: 'the solar arc (progressed Sun minus natal Sun) is added to every natal planet and angle.' It also contrasts the mechanics with sibling approaches ('all planets advance at the same rate'), making it unmistakable.

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?

Explicit WORKFLOW block names the prerequisite (asterwise_get_western_natal) and notes no follow-up step, and the DO NOT CONFUSE WITH section names two specific alternatives with the distinguishing criterion for each.

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

All Asterwise toolsInspect
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