Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Greene: Archetypal Figures

astroway_psychological_modern_greene_archetypal_figures
Read-onlyIdempotent

Generate archetypal figures based on Liz Greene’s modern psychological astrology from birth date, time, and place to interpret chart patterns.

Instructions

Archetypal patterns in the chart per Liz Greene.

[Group: Modern Psychological] [Endpoint: POST /v1/modern/greene/archetypal-figures] [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_greene_archetypal_figures"
  }
}

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
figuresNo
doctrineNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnly/false-destructive/idempotent, so the safety profile is covered, and an output schema exists. What the description uniquely adds is the cost ('10 credits, Tier 1'), which is genuinely useful for tool selection, plus the endpoint. It says nothing about what the reading contains or how deep it goes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, with the core purpose in the first line. But much of the length is boilerplate metadata (group, endpoint) rather than description, leaving the substance underspecified rather than efficient.

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?

The output schema relieves the description of explaining return values, and annotations cover safety. Still, a 13-parameter astrological calculation with 23% schema coverage needs more than a four-word purpose line; an agent cannot tell what inputs actually affect the archetypal-figure output or what distinguishes this from the other Greene endpoints.

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 coverage is only 23% across 13 parameters; the description merely restates the four required fields already listed in the schema's required array. It adds no meaning for zodiacType, houseSystem, ayanamsaId, ayanamsa, cosmogram, city or name — exactly the parameters where an agent needs guidance. No compensation for the coverage gap.

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?

States the resource ('Archetypal patterns in the chart per Liz Greene'), which at least identifies the technique and its author-school. But 'archetypal figures' is never unpacked (planets as gods? specific chart points?), and against siblings like greene_saturn_shadow, greene_parental_imagos, greene_lunar_myth and greene_individuation_path the description gives no basis for choosing this one.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance at all. The bracketed lines give endpoint, required fields and cost, but none of that tells an agent when this reading is the right one versus the four other Greene psychological tools.

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