AstroWay Astrology API (full catalogue)

Decode Dream Text

astroway_esoteric_dreams_decode

Read-onlyIdempotent

Scan dream narrative text for known symbols. Returns matched symbols with their meanings (recurring or single-event).

[Group: Esoteric] [Endpoint: POST /v1/esoteric/dreams/decode] [Required: text] [Cost: 10 credits (Tier 1)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "astroway_esoteric_dreams_decode"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`text`	No
`symbols`	No
`suggestion`	No
`symbolsFound`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 7, 2026

removedOutput schema / properties / suggestion / anyOf

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

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

changedOutput schema / properties / symbols / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "keyword": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "meaning": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "keyword": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "meaning": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / symbolsFound / anyOf

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

addedOutput schema / properties / symbolsFound / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / text / anyOf

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

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

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/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 description only needs to add context. It does so by disclosing the cost (10 credits, Tier 1) and the endpoint, and by stating that results are matched symbols with meanings classified as recurring or single-event — details not derivable from the safety hints.

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 functional sentence comes first with zero preamble, followed by a compact metadata block. Every line carries information; only the endpoint line is arguably low-value for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations and an output schema already covering safety and return shape, the definition supplies the remaining essentials: what the input should be, cost, and the nature of the result. Only the fallback behavior when no symbols match is unaddressed.

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 coverage is 50%: `fields` and `precision` are well documented in the schema, but `text` and `recurring` have no schema descriptions. The description restates that `text` is required and hints that `recurring` selects recurring versus single-event symbols, which is genuinely useful, but it leaves the exact semantics of `recurring` ambiguous and adds nothing about the text length bounds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource pair: it scans dream narrative text for known symbols and returns the matched symbols with meanings. That is clearly distinct from keyword-lookup siblings such as astroway_esoteric_dreams_symbol_keyword or recurring-themes tools, though the description never names those siblings explicitly.

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?

Usage is only implied: an agent can infer it should pass a full dream narrative rather than a keyword, but there is no explicit when-to-use statement, no exclusions, and no pointer to the sibling symbol-keyword or recurring-themes tools as alternatives.

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?