AstroWay Astrology API (full catalogue)

Decode Angel Number

astroway_esoteric_angel_numbers_decode

Read-onlyIdempotent

Decode a numeric sequence in optional life context. Returns pattern classification, exact match, and reduced single-digit meaning.

[Group: Esoteric] [Endpoint: POST /v1/esoteric/angel-numbers/decode] [Required: sequence] [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": {
      "sequence": "<sequence>"
    },
    "name": "astroway_esoteric_angel_numbers_decode"
  }
}

Input Schema

Name	Required	Description
`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.
`context`	No
`sequence`	Yes
`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
`context`	No
`pattern`	No
`sequence`	No
`reducedTo`	No
`exactMatch`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 7, 2026

removedOutput schema / properties / context / anyOf

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

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

changedOutput schema / properties / exactMatch / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "shortMeaning": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "shortMeaning": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / pattern / anyOf

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

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

removedOutput schema / properties / reducedTo / anyOf

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

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

removedOutput schema / properties / sequence / anyOf

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

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

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety behavior is covered. The description adds genuinely new operational context: the POST endpoint, the required parameter, and a cost of 10 credits (Tier 1), which matters for an agent budgeting calls. It does not say how 'context' influences the decoding or whether unknown sequences error out.

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 prose is a single efficient sentence with the core action front-loaded, followed by compact bracketed metadata for group, endpoint, required field, and cost. Every line carries value, though the metadata block is somewhat boilerplate.

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?

An output schema exists, yet the description still summarizes return shape, and cost plus required-field metadata fill the gaps an agent would otherwise guess at. The one real omission is what 'context' does to the result and how invalid sequences are handled, which is a modest gap for a read-only decoder.

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 documented inline, while 'sequence' and 'context' have no schema descriptions. The description partially compensates by framing sequence as a numeric sequence and context as an optional life context with no format or effect explained, so the gap is only half closed.

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 states a specific verb (Decode) and resource (a numeric sequence), and it enumerates the returned artifacts: pattern classification, exact match, and reduced single-digit meaning. That distinguishes it from siblings such as astroway_esoteric_angel_numbers_number or _today, though it never names an alternative explicitly.

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?

The phrase 'in optional life context' implies inputs but gives no when-to-use guidance, no conditions for picking this over astroway_esoteric_angel_numbers_by_life_path_n or _number, and no exclusions. An agent must infer routing from the name alone.

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?