Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Symbolic Directions

astroway_prognostics_symbolic_directions
Read-onlyIdempotent

Calculate symbolic directions to natal chart points for a target date using one-degree, Naibod, or solar-arc keys to assess time-based astrological trends.

Instructions

Calculate symbolic arc directions to natal points for a target date. Key: "one_degree" (default), "naibod", or "solar_arc" (the arc of the progressed Sun).

[Group: Prognostics] [Endpoint: POST /v1/symbolic-directions] [Cost: 50 credits (Tier 3)]

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": {
      "body": "<body>"
    },
    "name": "astroway_prognostics_symbolic_directions"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNatal chart plus a target date and the directional key: one degree per year, the Naibod rate, or the arc of the progressed Sun.

Output Schema

NameRequiredDescriptionDefault
arcNo
keyNo
housesNo
planetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • changedInput schema / properties / body / allOf
      Previous value: -[
      -  {
      -    "allOf": [
      -      {
      -        "additionalProperties": {
      -          "anyOf": [
      -            {},
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
      -        "properties": {
      -          "ayanamsa": {
      -            "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      -            "enum": [
      -              "fagan-bradley",
      -              "lahiri",
      -              "de-luce",
      -              "raman",
      -              "krishnamurti",
      -              "kp",
      -              "yukteshwar",
      -              "jn-bhasin",
      -              "true-citra",
      -              "djwhal-khul"
      -            ],
      -            "type": "string"
      -          },
      -          "ayanamsaId": {
      -            "type": [
      -              "number",
      -              "null"
      -            ]
      -          },
      -          "city": {
      -            "default": "",
      -            "type": "string"
      -          },
      -          "cosmogram": {
      -            "type": "boolean"
      -          },
      -          "date": {
      -            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      -            "type": "string"
      -          },
      -          "houseSystem": {
      -            "default": "P",
      -            "enum": [
      -              "P",
      -              "K",
      -              "R",
      -              "C",
      -              "E",
      -              "W",
      -              "B",
      -              "M",
      -              "O",
      -              "A",
      -              "T",
      -              "V",
      -              "D",
      -              "F",
      -              "G",
      -              "H",
      -              "I",
      -              "i",
      -              "L",
      -              "N",
      -              "Q",
      -              "S",
      -              "U",
      -              "X",
      -              "Y"
      -            ],
      -            "type": "string"
      -          },
      -          "latitude": {
      -            "maximum": 90,
      -            "minimum": -90,
      -            "type": "number"
      -          },
      -          "longitude": {
      -            "maximum": 180,
      -            "minimum": -180,
      -            "type": "number"
      -          },
      -          "name": {
      -            "default": "",
      -            "type": "string"
      -          },
      -          "time": {
      -            "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      -            "type": "string"
      -          },
      -          "timezone": {
      -            "description": "IANA 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.",
      -            "type": "string"
      -          },
      -          "timezoneOffset": {
      -            "anyOf": [
      -              {
      -                "maximum": 14,
      -                "minimum": -14,
      -                "type": "number"
      -              },
      -              {
      -                "type": "null"
      -              }
      -            ],
      -            "default": 0,
      -            "description": "Hours 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."
      -          },
      -          "zodiacType": {
      -            "enum": [
      -              "tropical",
      -              "sidereal"
      -            ],
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "date",
      -          "time",
      -          "latitude",
      -          "longitude"
      -        ],
      -        "type": "object"
      -      },
      -      {
      -        "additionalProperties": {
      -          "anyOf": [
      -            {},
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "properties": {
      -          "converse": {
      -            "type": "boolean"
      -          },
      -          "targetDate": {
      -            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      -            "type": "string"
      -          },
      -          "targetTime": {
      -            "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      -            "type": "string"
      -          },
      -          "targetTzOffset": {
      -            "type": [
      -              "number",
      -              "null"
      -            ]
      -          }
      -        },
      -        "required": [
      -          "targetDate"
      -        ],
      -        "type": "object"
      -      }
      -    ],
      -    "description": "Natal chart plus a target date for time-based calculations: progressions, directions, profections, returns."
      -  },
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "properties": {
      -      "key": {
      -        "enum": [
      -          "one_degree",
      -          "naibod",
      -          "solar_arc"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "allOf": [
      +      {
      +        "additionalProperties": {
      +          "anyOf": [
      +            {},
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
      +        "properties": {
      +          "ayanamsa": {
      +            "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      +            "enum": [
      +              "fagan-bradley",
      +              "lahiri",
      +              "de-luce",
      +              "raman",
      +              "krishnamurti",
      +              "kp",
      +              "yukteshwar",
      +              "jn-bhasin",
      +              "true-citra",
      +              "djwhal-khul"
      +            ],
      +            "type": "string"
      +          },
      +          "ayanamsaId": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "city": {
      +            "default": "",
      +            "type": "string"
      +          },
      +          "cosmogram": {
      +            "type": "boolean"
      +          },
      +          "date": {
      +            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +            "type": "string"
      +          },
      +          "houseSystem": {
      +            "default": "P",
      +            "enum": [
      +              "P",
      +              "K",
      +              "R",
      +              "C",
      +              "E",
      +              "W",
      +              "B",
      +              "M",
      +              "O",
      +              "A",
      +              "T",
      +              "V",
      +              "D",
      +              "F",
      +              "G",
      +              "H",
      +              "I",
      +              "i",
      +              "L",
      +              "N",
      +              "Q",
      +              "S",
      +              "U",
      +              "X",
      +              "Y"
      +            ],
      +            "type": "string"
      +          },
      +          "latitude": {
      +            "maximum": 90,
      +            "minimum": -90,
      +            "type": "number"
      +          },
      +          "longitude": {
      +            "maximum": 180,
      +            "minimum": -180,
      +            "type": "number"
      +          },
      +          "name": {
      +            "default": "",
      +            "type": "string"
      +          },
      +          "time": {
      +            "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      +            "type": "string"
      +          },
      +          "timezone": {
      +            "description": "IANA 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.",
      +            "type": "string"
      +          },
      +          "timezoneOffset": {
      +            "anyOf": [
      +              {
      +                "maximum": 14,
      +                "minimum": -14,
      +                "type": "number"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "default": 0,
      +            "description": "Hours 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."
      +          },
      +          "zodiacType": {
      +            "enum": [
      +              "tropical",
      +              "sidereal"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "date",
      +          "time",
      +          "latitude",
      +          "longitude"
      +        ],
      +        "type": "object"
      +      },
      +      {
      +        "additionalProperties": {
      +          "anyOf": [
      +            {},
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "properties": {
      +          "converse": {
      +            "type": "boolean"
      +          },
      +          "targetDate": {
      +            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +            "type": "string"
      +          },
      +          "targetTime": {
      +            "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      +            "type": "string"
      +          },
      +          "targetTzOffset": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "targetDate"
      +        ],
      +        "type": "object"
      +      }
      +    ],
      +    "description": "Natal chart plus a target date for time-based calculations: progressions, directions, profections, returns."
      +  },
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "properties": {
      +      "key": {
      +        "enum": [
      +          "one_degree",
      +          "naibod",
      +          "solar_arc"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  2. Addedv1.6.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context the annotations cannot carry: a 50-credit Tier 3 billing cost and the POST endpoint, which matters for planning. It says nothing about the volume or shape of what comes back, though the output schema absorbs most of that concern.

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?

Two substantive sentences followed by compact metadata lines; the operation and its key options are front-loaded with no padding. Every line carries information an agent can act on.

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

Completeness3/5

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

For a single-parameter tool with a rich nested schema, full parameter descriptions and an output schema, the description is adequate but thin on the one thing structured fields cannot supply: how this technique relates to its prognostics siblings. The core call path is clear, so the gap is not disqualifying.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by glossing the directional key values: one_degree is flagged as the default and solar_arc is defined as the arc of the progressed Sun, which the bare enum does not convey. Naibod is left unexplained, which keeps it from a 5.

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

Purpose4/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: "Calculate symbolic arc directions to natal points for a target date." That is far more precise than the title alone and an agent can identify the operation. It stops short of differentiating itself from close siblings such as primary directions or secondary progressions, which share the same natal-plus-target-date shape.

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 guidance and no mention of alternatives, even though the sibling list contains primary_directions and progressions that an agent could easily confuse with this tool. The phrase "for a target date" implies a forecasting context but does not tell the agent when this technique is the right choice over its neighbours.

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