AstroWay Astrology API (full catalogue)

Sphaera Barbarica

astroway_helg_sphaera_barbarica

Read-onlyIdempotent

Constellations beyond the zodiac.

[Group: Hellenistic: Greenbaum tradition] [Endpoint: POST /v1/hellenistic/greenbaum/sphaera-barbarica] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

(Cursor-friendly alias for astroway_hellenistic_greenbaum_sphaera_barbarica.)

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`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.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	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.
`cosmogram`	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.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	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.

Output Schema

Name	Required	Description	Default
`notes`	No
`angles`	No
`source`	No
`doctrine`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 7, 2026

removedInput schema / properties / ayanamsaId / anyOf

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

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

changedOutput schema / properties / angles / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "asc": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "angle": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "decan": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "decanRuler": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "longitude": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "mc": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "angle": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "decan": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "decanRuler": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "longitude": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "asc": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "angle": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "decan": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "decanRuler": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "longitude": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "mc": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "angle": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "decan": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "decanRuler": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "longitude": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / disclaimer / anyOf

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

addedOutput schema / properties / disclaimer / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / doctrine / anyOf

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

addedOutput schema / properties / doctrine / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / notes / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / source / anyOf

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

addedOutput schema / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds genuinely non-annotation information: a per-call cost of 10 credits (Tier 1), the HTTP endpoint, and the four required inputs. It says nothing about what the computation yields or any failure modes, so it adds useful operational context but limited behavioral depth.

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 is short, front-loaded with the subject phrase, and uses bracketed metadata lines that are easy to scan. Every line carries information (group, endpoint, required inputs, cost, alias) with no filler prose. The trade-off is that the compressed, template-like format leaves the substance thin.

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?

For a 15-parameter astrological computation whose subject is obscure to most agents, the description never explains what a Sphaera Barbarica result actually contains or how sidereal versus tropical and the ayanamsa/house-system options affect it. The presence of an output schema reduces the burden of describing return values, and the cost/required-field notes help, but an agent still cannot predict the response shape or choose sensible defaults from this text alone.

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 33% across 15 parameters, so the description needs to compensate and does not. It merely repeats the four required fields (date, time, latitude, longitude) that the schema already marks as required, and is silent on the undocumented parameters — city, name, cosmogram, ayanamsaId, zodiacType, and the 25-value houseSystem enum — leaving an agent no guidance on defaults or interaction between `timezone` and `timezoneOffset` beyond what the schema itself says.

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?

The description gives a resource-level phrase, "Constellations beyond the zodiac," which identifies the subject matter (extra-zodiacal constellations / paranatellonta) but supplies no verb and no statement of what the tool computes or returns. The parenthetical alias note does distinguish it from `astroway_hellenistic_greenbaum_sphaera_barbarica` by declaring them interchangeable, which helps sibling differentiation, but the core purpose remains a topic label rather than an action.

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 alias sentence answers the routing question for exactly one sibling — an agent knows this is the cursor-friendly duplicate of the long-name Greenbaum tool and can pick either. The group tag "Hellenistic: Greenbaum tradition" places it among the helg/hellenistic tools. However, there is no guidance on when to reach for Sphaera Barbarica versus related techniques in the same family (zodiacal decans, dodekatemoria, temple doctrine), and no stated 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?