Skip to main content
Glama
Sign In

AstroWay Astrology API (full catalogue)

by info.astroway
OverviewDiscussionsAdmin

Populus: The People

astroway_geomancy_populus
Read-onlyIdempotent

Crowd, gathering, public.

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

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new operational facts beyond the annotations — the POST endpoint and a 10-credit Tier 1 cost — which is useful for call budgeting, but it says nothing about what a call returns beyond the presence of an output schema.

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?

Brevity is not wasted wording — the bracketed group/endpoint/cost tags are scannable and informative. But the front-loaded content is a bare keyword list rather than a statement of purpose, so the structure is efficient without being informative where it matters most.

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?

With an output schema, full parameter documentation, and rich annotations, the structural data covers most of what an agent needs to execute a call. What remains missing is conceptual: what a geomancy figure lookup returns and how to pick this figure over its siblings, which no structured field supplies.

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?

Both parameters (fields, precision) have 100% schema description coverage, so the schema carries the meaning and the baseline of 3 applies. The description adds no additional context about compact mode, defaults, or when to use response shaping, so it neither helps nor compensates.

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 only a keyword gloss for the figure ("Crowd, gathering, public"), which restates the name/title in synonyms rather than stating a verb+resource such as "returns the interpretation of the Populus geomantic figure." An agent familiar with geomancy could infer the intent from the name and the [Group: Geomancy (Agrippa)] tag, but the definition itself never says what the tool produces.

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 and no differentiation from the 15 sibling geomancy figure tools (albus, puer, via, etc.). The keyword gloss weakly implies the domain (crowds, gatherings, public matters), but the agent is left to supply all the reasoning about which figure applies to a query.

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