Angel Numbers MCP Server by RoxyAPI

Daily angel number - Angel number of the day API

post_angel_numbers_daily

Read-only

Get the angel number of the day with full meaning and interpretation. Returns a deterministic angel number based on the current date (or a provided seed date), ensuring all users see the same number for any given day. Includes complete spiritual, love, career, money, and twin flame interpretations plus a biblical perspective and a shadow reading. Perfect for daily guidance features, push notifications, content generation, and angel number widget integrations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`seed`	No	Optional seed for reproducible readings. Same seed + same date = same angel number every time. Pass any unique identifier (userId, email hash, session token). Omit for anonymous daily readings.
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`seed`	Yes
`type`	Yes
`title`	Yes
`energy`	Yes
`number`	Yes
`shadow`	Yes
`meaning`	Yes
`biblical`	Yes
`keywords`	Yes
`digitRoot`	Yes
`actionSteps`	Yes
`affirmation`	Yes
`coreMessage`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "actionSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "affirmation": {
+      "type": "string"
+    },
+    "biblical": {
+      "type": "string"
+    },
+    "coreMessage": {
+      "type": "string"
+    },
+    "date": {
+      "type": "string"
+    },
+    "digitRoot": {
+      "type": "number"
+    },
+    "energy": {
+      "type": "string"
+    },
+    "keywords": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "meaning": {
+      "properties": {
+        "career": {
+          "type": "string"
+        },
+        "love": {
+          "type": "string"
+        },
+        "money": {
+          "type": "string"
+        },
+        "spiritual": {
+          "type": "string"
+        },
+        "twinFlame": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "spiritual",
+        "love",
+        "career",
+        "money",
+        "twinFlame"
+      ],
+      "type": "object"
+    },
+    "number": {
+      "type": "string"
+    },
+    "seed": {
+      "type": "string"
+    },
+    "shadow": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "seed",
+    "number",
+    "title",
+    "coreMessage",
+    "type",
+    "digitRoot",
+    "energy",
+    "meaning",
+    "biblical",
+    "shadow",
+    "keywords",
+    "affirmation",
+    "actionSteps"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

First observedJul 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the number is deterministic per date/seed, all users see the same number for a given day, and the response includes multiple interpretation domains. This goes beyond the annotations without contradicting them.

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 description is a single paragraph that front-loads the primary purpose and then adds deterministic behavior, content coverage, and use cases. It is efficient and each sentence adds useful information, though the closing use-case list is somewhat promotional and could be trimmed without losing essential guidance.

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?

Given the output schema exists and all four parameters are optional with full schema descriptions, the description is sufficiently complete for an agent to call the tool correctly. It covers determinism, language fallback context is in the schema, and the response contents are summarized. No critical behavioral gaps like output format or side effects remain unexplained.

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%, so the parameter semantics are already fully documented in the input schema. The description reinforces the seed behavior ('deterministic angel number based on the current date or a provided seed date') but does not add meaning beyond the schema's parameter descriptions. Baseline 3 applies.

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 and resource: 'Get the angel number of the day with full meaning and interpretation.' It clearly describes the tool's core function and its deterministic date-based behavior. However, it does not explicitly name or contrast sibling tools, so differentiation from get_angel_numbers_lookup or get_angel_numbers_number is only implied by the 'daily' framing.

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?

The description includes use cases ('Perfect for daily guidance features, push notifications, content generation, and angel number widget integrations'), which imply when an agent might choose this tool. It provides no explicit when-to-use versus alternatives guidance, no exclusions, and no mention of the sibling tools that might be more appropriate for other lookup types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Angel Numbers MCP Server by RoxyAPI 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?