Skip to main content
Glama
Sign In

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

Western Secondary Progressions

asterwise_get_western_secondary_progressions
Read-onlyIdempotent

Secondary progressed chart using the day-for-a-year method. Each day after birth symbolises one year of life (1 ephemeris day = 1 tropical year = 365.2421904 days). Returns all 10 progressed planet positions, progressed Ascendant and MC, and the solar arc.

WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: asterwise_get_western_solar_arc — compare uniform arc vs individual motion.

INPUT CONTRACT: birth — WesternBirthData. target_date (optional YYYY-MM-DD) — the date to progress to. Defaults to today.

DO NOT CONFUSE WITH: asterwise_get_western_solar_arc — all planets move by one uniform arc. asterwise_get_western_transits_daily — real-time sky, not symbolic progression.

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

Input Schema

NameRequiredDescriptionDefault
birthYesBirth data for Western astrology tools (tropical zodiac).
target_dateNoDate to progress 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 progress 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 read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: the symbolic day-for-a-year computation method, the returned chart points, and the workflow relationship to natal and solar arc tools. It does not cover auth, rate limits, or error behavior, deferring those to the docs link, so it is strong but not exhaustive.

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 definition is front-loaded with the core method and output, then organized into WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH sections. Every sentence carries routing or contract information, with no filler.

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?

Given the nested birth object, the presence of an output schema, and the rich annotations, the description supplies the missing conceptual context: what the progression means, how it differs from solar arc and transits, and the workflow order. It also links to the full output and error contract, so an agent has enough to call it correctly.

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%, so the schema already documents birth, target_date, and response_format. The description repeats the target_date format and default but adds no syntax or meaning beyond what the schema provides, which is the baseline expectation for fully covered parameters.

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 verb and resource: it computes a secondary progressed chart using the day-for-a-year method, and it specifies the exact outputs (10 progressed planets, progressed Ascendant and MC, and solar arc). It also explicitly distinguishes itself from the two closest siblings, solar arc and daily transits.

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?

It provides an explicit workflow with BEFORE: asterwise_get_western_natal and AFTER: asterwise_get_western_solar_arc. The DO NOT CONFUSE WITH section names the alternative tools and explains the conceptual difference, so an agent can route correctly without inference.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources