Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Greene: Parental Imagos

astroway_psychological_modern_greene_parental_imagos
Read-onlyIdempotent

Analyze parental imagos through Greene's modern psychological astrology to uncover unconscious mother and father patterns from a birth chart.

Instructions

Parental imagos analysis.

[Group: Modern Psychological] [Endpoint: POST /v1/modern/greene/parental-imagos] [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_parental_imagos"
  }
}

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
disclaimerNo
shadowMarkersNo
exteriorParentNo
interiorParentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so safety is covered. The description does add real behavioral context not in annotations: the POST endpoint, the four required inputs, and a concrete cost of 10 credits (Tier 1). It does not explain what the analysis returns, but with annotations and an output schema that is acceptable.

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?

The text is compact and the metadata lines are scannable, but the opening sentence carries almost no information while consuming the front-loaded position. Structure is fine; content density of the prose is the problem.

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

Completeness4/5

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

Annotations cover the safety profile and an output schema exists, so return values need not be described. The description adds endpoint, required inputs and cost, which is enough for an agent to call it correctly. Only the ambiguity of what 'parental imagos' means is left unresolved, keeping it short of a 5.

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, so the description must compensate and does not. It merely repeats the four required fields already listed in the schema's `required` array, saying nothing about ayanamsa, zodiacType, houseSystem, cosmogram, or how latitude/longitude interact with timezone.

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

Purpose2/5

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

The description is 'Parental imagos analysis,' which essentially restates the tool's title ('Greene: Parental Imagos'). 'Analysis' is the only added word and conveys no specific resource or operation; an agent cannot tell what the tool actually produces or how it differs from sibling Greene tools like archetypal_figures or saturn_shadow.

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

Usage Guidelines1/5

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

There is no statement of when to use this tool, when not to, or which sibling (e.g. greene_archetypal_figures, greene_individuation_path) is the alternative. The bracketed metadata lines give endpoint, required params and cost, but no selection guidance.

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