Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Arroyo: Cycle of Becoming

astroway_psychological_modern_arroyo_cycle_of_becoming
Read-onlyIdempotent

Calculate Arroyo's evolutionary cycle of becoming from birth date, time, and coordinates to reveal psychological growth phases and developmental turning points.

Instructions

Arroyo's evolutionary cycle.

[Group: Modern Psychological] [Endpoint: POST /v1/modern/arroyo/cycle-of-becoming] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

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": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_psychological_modern_arroyo_cycle_of_becoming"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
sourceNo
doctrineNo
fullCycleNo
currentAgeNo
disclaimerNo
currentPhaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.7/5.0
Behavior3/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 usefully adds cost (10 credits, Tier 1) and the required-input set, but says nothing about what the response contains or how the cycle is computed.

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?

Four compact, front-loaded metadata lines with no filler. Efficient, though the substantive sentence is very thin relative to the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter psychological calculation with an output schema, the description omits what the 'cycle of becoming' returns, defaults, and how it differs from the Rudhyar counterpart. Endpoint and cost are covered, but the substance an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 23% across 13 parameters, and the description compensates with nothing beyond the four required fields. Nine parameters (city, name, ayanamsaId, cosmogram, zodiacType, houseSystem, etc.) are left entirely to the bare schema, including the 25-value houseSystem code list which needs explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The line "Arroyo's evolutionary cycle" identifies the resource (an Arroyo-style evolutionary cycle) and the name adds 'psychological modern', but it never says what the tool actually computes or returns. Nothing distinguishes it from the close sibling astroway_psychological_modern_rudhyar_cycles_of_becoming, which appears to compute a near-identical concept.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this over the four other Arroyo psychological tools or the Rudhyar cycles sibling. The bracketed metadata gives group and endpoint but no selection criteria or prerequisites.

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

Deploy Server

Other Tools