AstroWay Astrology API (full catalogue)

Local Space Influence Zone

astroway_geo_local_space_influence_zone

Read-onlyIdempotent

Calculate the local space influence zone lines for a chart relocated to a specific city: lines on the map showing planet directions from that location.

[Group: Astro-Geography] [Endpoint: POST /v1/local-space/influence-zone] [Required: latitude, longitude, azimuth] [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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "azimuth": "<azimuth>"
    },
    "name": "astroway_geo_local_space_influence_zone"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`azimuth`	Yes
`latitude`	Yes
`halfAngle`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`maxDistDeg`	No

Output Schema

Name	Required	Description	Default
`count`	No
`polygon`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 7, 2026

removedInput schema / properties / azimuth / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / azimuth / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedInput schema / properties / halfAngle / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / halfAngle / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedInput schema / properties / latitude / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / latitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedInput schema / properties / longitude / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / longitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedInput schema / properties / maxDistDeg / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / maxDistDeg / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / polygon / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "lat": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "lng": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "lat": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "lng": {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's added value is operational: the POST endpoint, the enforced required parameters, and a concrete cost of 50 credits (Tier 3). That cost disclosure is genuinely useful for an agent budgeting calls, though nothing is said about output volume or limits.

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?

The definition sentence comes first and the bracketed metadata lines are compact and scannable. The endpoint and group tags are slightly redundant given the tool name, but overall there is little waste.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. However, for a 7-parameter computational tool with two undocumented geometric parameters (halfAngle, maxDistDeg), the description leaves the agent guessing about the core calculation inputs.

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 29%; only 'fields' and 'precision' are documented. The description merely repeats the three required names (latitude, longitude, azimuth) without explaining what azimuth means here or what halfAngle and maxDistDeg control, leaving four parameters semantically opaque.

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 and resource ('Calculate the local space influence zone lines') and clarifies the output with 'lines on the map showing planet directions from that location'. It does not explicitly contrast with its closest sibling, astroway_geo_local_space, so the agent must infer the distinction.

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

Usage Guidelines3/5

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

The phrase 'for a chart relocated to a specific city' implies the use case, but there is no explicit when-to-use guidance, no mention of alternatives like astroway_geo_local_space or astroway_geo_acg_zones, and no prerequisites or exclusions.

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

All AstroWay Astrology API (full catalogue) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?