Skip to main content
Glama
Sign In

AstroWay Astrology API (full catalogue)

by info.astroway
OverviewDiscussionsAdmin

Coniunctio: Conjunction

astroway_geomancy_coniunctio
Read-onlyIdempotent

Union, meeting, partnership.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
figureNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes genuinely new behavioral information — the credit cost (10 credits, Tier 1), the POST endpoint and the source system (Agrippa) — but says nothing about what the response contains or whether the result varies per call.

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 keyword line is front-loaded, with metadata brackets cleanly separated, so nothing is wasted. However, the brevity is achieved by omitting the actual operation, not by efficient phrasing, and the fragment style conveys little.

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 and the input schema is fully self-documenting, so return values and parameters need not be spelled out. What remains missing is the one thing the description must carry: what invoking this figure actually produces for the caller and how it differs from its geomancy siblings.

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 optional parameters (fields, precision) are documented in the schema with examples and defaults. The description adds no parameter information at all, so the baseline 3 applies rather than any credit.

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 keyword gloss of the figure's meaning ("Union, meeting, partnership") that restates the title "Coniunctio: Conjunction" rather than stating what the tool does. There is no verb and no statement of what is returned — a reading of the figure, a generated interpretation, or raw correspondences — so an agent cannot tell the operation apart from the other fifteen geomancy sibling tools except by figure 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?

No guidance is given about when to call this specific figure rather than another geomancy tool, nor whether a question or context is required. The only routing signal available is the semantic association of "union/partnership," which the agent must infer.

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) toolsInspect
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