astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

CCG Analysis

astroway_geo_ccg_analysis

Read-onlyIdempotent

Analyze Cyclo-Carto-Graphy (CCG) by calculating progressed ACG lines at a target date, including mundane/local aspects and latitude crossings for geo-astrology readings.

Instructions

Analyse Cyclo-Carto-Graphy (CCG) lines: progressed ACG lines at a target date with mundane/local aspects and latitude crossings.

[Group: Astro-Geography] [Endpoint: POST /v1/ccg-analysis] [Cost: 100 credits (Tier 4)]

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_geo_ccg_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.

Output Schema

Name	Required	Description	Default
`meta`	No
`mcShift`	No
`mundaneAspects`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.1Nov 9, 2026

changedInput schema / properties / body / allOf

Previous value: -[
-  {
-    "description": "Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.",
-    "properties": {
-      "natal": {
-        "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"
-      }
-    },
-    "required": [
-      "natal"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "fastPlanetsOnly": {
-        "type": "boolean"
-      },
-      "latitude": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "orb": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "point": {
-        "properties": {
-          "lat": {
-            "maximum": 90,
-            "minimum": -90,
-            "type": "number"
-          },
-          "lng": {
-            "maximum": 180,
-            "minimum": -180,
-            "type": "number"
-          }
-        },
-        "required": [
-          "lat",
-          "lng"
-        ],
-        "type": "object"
-      },
-      "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"
-  }
-]New value: +[
+  {
+    "description": "Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.",
+    "properties": {
+      "natal": {
+        "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"
+      }
+    },
+    "required": [
+      "natal"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "fastPlanetsOnly": {
+        "type": "boolean"
+      },
+      "latitude": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "orb": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "point": {
+        "properties": {
+          "lat": {
+            "maximum": 90,
+            "minimum": -90,
+            "type": "number"
+          },
+          "lng": {
+            "maximum": 180,
+            "minimum": -180,
+            "type": "number"
+          }
+        },
+        "required": [
+          "lat",
+          "lng"
+        ],
+        "type": "object"
+      },
+      "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"
+  }
+]

Addedv1.6.0Oct 24, 2026

TDQS

B3.4/5.0

Behavior4/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 adds genuinely new operational context the annotations cannot: the endpoint (POST /v1/ccg-analysis) and a concrete cost (100 credits, Tier 4), which matters for an agent budgeting tool calls. It stops short of describing the returned content or any limits on computation size.

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?

One front-loaded sentence states the analysis and its components, followed by a compact bracketed metadata block for group, endpoint and cost. There is no filler, though the description body is terse relative to the underlying parameter surface.

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 moderately complex tool (natal chart plus target date, orb and optional point filter) the definition identifies what is computed and what it costs, and an output schema exists to cover return values. However it says nothing about how the orb or point parameters shape the results, nor about the distinction from natal A*C*G, which an agent would need to choose and configure it confidently.

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 deeply documented natal body, targetDate, orb, point and fastPlanetsOnly fields already carry their own meaning. The description names the key domain concepts (target date, aspects, latitude crossings) but adds no format, default, or interaction details beyond the schema; baseline 3 applies.

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 gives a specific verb (Analyse) and a precisely delimited resource (Cyclo-Carto-Graphy / progressed A*C*G lines at a target date), then enumerates the analysis components: mundane/local aspects and latitude crossings. The word 'progressed' implicitly separates it from natal A*C*G work, so an agent can broadly place it, though no sibling is named explicitly.

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 or when-not-to-use guidance, no prerequisites (e.g. that a natal chart plus a target date are needed), and no routing advice versus related geo tools such as the plain ACG variants. The target-date scope hints at the use case, but nothing is stated about alternatives.

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

Deploy Server