AstroWay Astrology API (full catalogue)

by info.astroway

Overview Discussions Admin

Laetitia: Joy

astroway_geomancy_laetitia

Read-onlyIdempotent

Happiness, optimism, healing.

[Group: Geomancy (Agrippa)] [Endpoint: POST /v1/geomancy/laetitia] [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_laetitia"
  }
}

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the remaining burden is light. The description adds genuinely useful operational context — the POST endpoint and a cost of 10 credits (Tier 1) — which an agent needs for budgeting and batching decisions. It does not explain what the call actually produces, but an output schema exists to cover that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the bracketed metadata is cleanly formatted, so nothing is wasted. However, the leading sentence is evocative rather than informative, so the most valuable information (endpoint, cost) sits after a line that does not orient the agent.

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 low-parameter, read-only lookup with an output schema and clear annotations, the definition covers cost, endpoint, and domain. What is missing is the one thing an agent most needs: what a request returns conceptually (the figure's meaning/interpretation) and why one would ask for Laetitia specifically.

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 in the schema with examples and sensible defaults. The description adds nothing about parameters, but the baseline of 3 applies when the schema does the full job.

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?

The description is a set of thematic keywords ("Happiness, optimism, healing") that restates the title "Laetitia: Joy" rather than stating what the tool does. Only the metadata tag "Group: Geomancy (Agrippa)" hints that this returns a geomantic figure's reading, and that must be inferred from the sibling list.

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 statement of when to select Laetitia over the fifteen other geomancy figure tools, nor any prerequisite or query-intent guidance. The group label implies the domain but gives no selection criteria.

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?