AstroWay Astrology API (full catalogue)

by info.astroway

Overview Discussions Admin

Albus: White

astroway_geomancy_albus

Read-onlyIdempotent

Wisdom, peace, clarity.

[Group: Geomancy (Agrippa)] [Endpoint: POST /v1/geomancy/albus] [Cost: 10 credits (Tier 1)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_geomancy_albus"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`figure`	No
`source`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026

changedOutput schema / properties / figure / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "divinatory": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "element": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "english": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "latin": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "meaning": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "nature": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "negative": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "pattern": {
-        "anyOf": [
-          {
-            "items": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "positive": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "ruler": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sign": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "slug": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "divinatory": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "element": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "english": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "latin": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "meaning": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "nature": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "negative": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "pattern": {
+        "anyOf": [
+          {
+            "items": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "positive": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "ruler": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sign": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "slug": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "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.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's real contribution is the cost (10 credits, Tier 1) and the POST endpoint, which is useful operational context an agent cannot get from annotations. It says nothing about what a reading contains or how the figure is derived, but with a full output schema that gap is partially mitigated.

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 compact and front-loaded, with cost and endpoint presented in a scannable bracketed format and no padding. The keyword line is thin in value but not verbose, so there is little waste to penalize.

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?

The tool is simple (two optional params, output schema present), so full return-value explanation is not required. Still, an agent reading this description alone cannot tell whether it returns a generated reading, a hexagram-like figure, or an interpretive text, and the keyword line substitutes mood for function.

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% and both parameters (fields, precision) are documented with examples and rationale in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

"Wisdom, peace, clarity" is a list of thematic keywords for the Albus geomantic figure, not a statement of what the tool does. The only operational signal is the bracketed group/endpoint metadata, from which an agent must infer that this returns an Albus geomancy reading. Among fifteen sibling geomancy figure tools, the description gives no basis for distinguishing Albus's operation from Amissio's or Puella's beyond the name.

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, no conditions, and no mention of alternatives among the many geomancy siblings. The group label implies a divination context, but nothing tells the agent when to select Albus versus another figure or versus a broader geomancy tool.

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?