Angel number meanings and repeating sequences like 111, 222, 333 for AI agents.
Scored across 4 tools
get_angel_numbers_number and get_angel_numbers_lookup overlap substantially—both return full spiritual/love/career/money/twin-flame interpretations for a number, differing only in that lookup handles arbitrary sequences with a digit-root fallback. The catalog tool is distinct, but the boundary between the two meaning-retrieval tools could cause misselection.
All names share the angel_numbers stem with consistent get_/post_ verb prefixes, which is predictable. However, the redundant prefix plus suffixes (_lookup, _number, _daily) is slightly awkward and makes the base tool and the specific-number tool visually similar.
Four tools is a well-scoped set for a read-only angel number API, covering catalog, lookup, specific meaning, and daily content without redundancy or bloat.
The surface covers listing with type filtering, arbitrary-number analysis, specific-number lookup, and date-based daily selection—a coherent read-only lifecycle. Minor gap: no explicit category/browse-by-pattern tool, but type filtering largely covers it.
Retrieve the angel number catalog with summary information. Returns 75+ angel numbers covering root digits (0-9), master numbers (11, 22, 33), double digits (44-99), triple repeating (111-999), quad repeating (1111-9999), the mirror families (X0X like 101-909, X1X, four-digit mirrors like 1212-2121), palindromes (1221, 1331), compound sequences (911, 1122), and sequential numbers (123, 1234). Supports optional type filtering. Perfect for building angel number explorer apps, reference guides, and spiritual databases.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
| type | No | Filter results by angel number pattern type. "repeating" returns numbers like 111, 444, 7777. "sequential" returns patterns like 1234. "mirror" returns palindrome or alternating patterns like 1212, 717. "master" returns 11, 22, 33. "root" returns single digits 0-9. "compound" returns mixed sequences with no pure pattern like 911, 1122. | |
| limit | No | Maximum items to return per page. Range: 1-50, default 20. | |
| offset | No | Number of items to skip for pagination. Default 0. | |
| 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. |
| Name | Required | Description |
|---|---|---|
| limit | Yes | |
| total | Yes | |
| offset | Yes | |
| numbers | Yes |
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 useful scope context (75+ entries, the pattern families covered), but says nothing about pagination defaults, ordering, or rate limits beyond what the schema states.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose is front-loaded in the first sentence and the second sentence efficiently conveys catalog breadth. However, the long enumeration of number families (root, master, double, triple, quad, mirrors, palindromes, compound, sequential) largely duplicates the type enum descriptions, and the final app-marketing sentence does not earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value detail is unnecessary, and the description correctly frames this as a summary listing. Combined with 100% schema coverage and read-only annotations, an agent has enough to call it correctly; only the lack of sibling routing and pagination behavior keeps it from a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so each of the five parameters (lang, type, limit, offset, compact) is already fully documented with enums, defaults, and ranges. The description only echoes 'optional type filtering' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Retrieve the angel number catalog with summary information') and clarifies it is the full listing rather than a single-number lookup, which implicitly separates it from get_angel_numbers_number. It never names the sibling tools explicitly, so the differentiation is inferred rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no when-to-use guidance relative to the three sibling tools (lookup, number, daily). The closing sentence ('Perfect for building angel number explorer apps, reference guides, and spiritual databases') is audience marketing, not usage routing, and 'Supports optional type filtering' restates a schema capability rather than a selection condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Smart angel number analysis that works for ANY number sequence, not just known angel numbers. Automatically classifies the pattern type (repeating, sequential, mirror, master, root, compound), calculates the numerology digit root, checks the database for a known meaning, and provides the foundational digit root interpretation (with full spiritual, love, career, money, and twin flame guidance) as a fallback. An optional context parameter adds a note tailored to where the number was seen. Perfect for synchronicity tracking apps where users enter arbitrary number sequences they encounter.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
| number | Yes | Number sequence to analyze (1-8 digits). Can be any number the user has encountered: clock times (1111), addresses (717), receipts (888), license plates (4444), or any repeating pattern. | |
| 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. | |
| context | No | Where the number was seen. When supplied, the response adds a contextNote tailoring the reading to the sighting: clock (a glanced time), receipt (a purchase), license-plate (in transit), phone (a call or notification), address (a home or place), price (a total or amount). |
| Name | Required | Description |
|---|---|---|
| type | Yes | |
| digits | Yes | |
| number | Yes | |
| digitRoot | Yes | |
| contextNote | No | |
| isRepeating | Yes | |
| isPalindrome | Yes | |
| knownMeaning | Yes | |
| uniqueDigits | Yes | |
| digitRootMeaning | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the operation readOnly and non-destructive, and the description adds useful behavioral context: it classifies pattern type, calculates digit root, checks the database, and provides a fallback interpretation. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core capability, followed by a concise pipeline summary and a targeted use case. It is dense but not padded; minor trimming of the opening 'Smart' would improve it slightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich schema, output schema, and readOnly annotations, the description is nearly complete for correct invocation. It omits explicit sibling routing, but the 'not just known angel numbers' clarification provides enough guidance for an agent to distinguish it from get_angel_numbers and related tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All four parameters are fully described in the schema with types, enums, examples, and defaults, so the description carries little additional parameter burden. It adds only the contextNote behavior, which the schema already documents.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource: analyze any number sequence, not just known angel numbers. It clearly differentiates the tool from sibling lookups by emphasizing support for arbitrary user-entered sequences rather than only canonical angel numbers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a clear use case: synchronicity tracking apps where users encounter arbitrary number sequences. It does not explicitly name sibling tools or state when to prefer them, but the 'ANY number sequence' framing strongly implies when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the full meaning and interpretation for a specific angel number. Returns detailed spiritual, love, career, money, and twin flame interpretations, plus a biblical perspective and a shadow reading, along with keywords, affirmation, and actionable steps. Covers 75+ angel numbers including 111, 222, 333, 444, 555, 666, 777, 888, 999, 1111, 1212, 1234, and more, across every major angel number pattern.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
| number | Yes | Angel number sequence to look up (e.g., "111", "444", "1212", "1234"). Must match an entry in the database. | |
| 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. |
| Name | Required | Description |
|---|---|---|
| type | Yes | |
| title | Yes | |
| energy | Yes | |
| number | Yes | |
| shadow | Yes | |
| meaning | Yes | |
| biblical | Yes | |
| keywords | Yes | |
| digitRoot | Yes | |
| actionSteps | Yes | |
| affirmation | Yes | |
| coreMessage | Yes |
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 useful payload context (which interpretation sections come back), but says nothing about failure behavior when the number is absent from the database or what 'lanch' fallback means beyond what the schema states. Adequate, not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose in the first sentence, followed by one dense sentence on the return contents. The trailing enumeration '111, 222, 333, 444, 555, 666, 777, 888, 999, 1111, 1212, 1234, and more' is padding that the schema example already conveys, costing a little tightness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not explain return shapes, and annotations plus a 100%-covered schema carry params and safety. What remains thin is discovery and error guidance: how an agent finds valid numbers (the listing/lookup siblings) or what happens on a miss. Otherwise complete for a simple read-by-key tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with per-parameter descriptions for lang, number, and compact, so the baseline is 3. The description only echoes the 'number' parameter and the valid-number universe; it adds no syntax, format, or interaction guidance beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Get the full meaning and interpretation for a specific angel number.' The scope of what is returned (spiritual, love, career, money, twin flame, biblical, shadow) is enumerated, so the agent knows exactly what this call yields. It never differentiates itself from the sibling 'get_angel_numbers_lookup', which reads as the same operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by 'for a specific angel number' and the coverage list ('75+ angel numbers including 111...'), so an agent can infer this is the per-number detail call versus a listing tool. There is no explicit when-to-use/when-not-to-use statement and no mention of the near-identical sibling 'get_angel_numbers_lookup', leaving a real risk of wrong-tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| 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. |
| Name | Required | Description |
|---|---|---|
| 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 |
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.
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.
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_angel_numbers2 fields changedInput schema / properties / offset / defaultAdded value: +0Input schema / properties / offset / minimumAdded value: +0get_angel_numbers3 fields changedInput schema / properties / offset / defaultRemoved value: -0Input schema / properties / offset / minimumRemoved value: -0Input schema / properties / offset / typePrevious value: -[
- "integer",
- "null"
-]New value: +"integer"get_angel_numbers1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "limit": {
+ "type": "number"
+ },
+ "numbers": {
+ "items": {
+ "properties": {
+ "coreMessage": {
+ "type": "string"
+ },
+ "digitRoot": {
+ "type": "number"
+ },
+ "energy": {
+ "type": "string"
+ },
+ "keywords": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "number": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "number",
+ "title",
+ "coreMessage",
+ "type",
+ "digitRoot",
+ "keywords",
+ "energy"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "offset": {
+ "type": "number"
+ },
+ "total": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "total",
+ "limit",
+ "offset",
+ "numbers"
+ ],
+ "type": "object"
+}get_angel_numbers_lookup1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "contextNote": {
+ "type": "string"
+ },
+ "digitRoot": {
+ "type": "number"
+ },
+ "digitRootMeaning": {
+ "properties": {
+ "affirmation": {
+ "type": "string"
+ },
+ "coreMessage": {
+ "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"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "number",
+ "title",
+ "coreMessage",
+ "meaning",
+ "keywords",
+ "affirmation"
+ ],
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "digits": {
+ "type": "number"
+ },
+ "isPalindrome": {
+ "type": "boolean"
+ },
+ "isRepeating": {
+ "type": "boolean"
+ },
+ "knownMeaning": {
+ "properties": {
+ "actionSteps": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "affirmation": {
+ "type": "string"
+ },
+ "biblical": {
+ "type": "string"
+ },
+ "coreMessage": {
+ "type": "string"
+ },
+ "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"
+ },
+ "shadow": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "title",
+ "coreMessage",
+ "energy",
+ "keywords",
+ "meaning",
+ "biblical",
+ "shadow",
+ "affirmation",
+ "actionSteps"
+ ],
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "number": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ },
+ "uniqueDigits": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "number",
+ "type",
+ "digitRoot",
+ "digits",
+ "uniqueDigits",
+ "isPalindrome",
+ "isRepeating",
+ "knownMeaning",
+ "digitRootMeaning"
+ ],
+ "type": "object"
+}get_angel_numbers_number1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "actionSteps": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "affirmation": {
+ "type": "string"
+ },
+ "biblical": {
+ "type": "string"
+ },
+ "coreMessage": {
+ "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"
+ },
+ "shadow": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "number",
+ "title",
+ "coreMessage",
+ "type",
+ "digitRoot",
+ "keywords",
+ "energy",
+ "meaning",
+ "biblical",
+ "shadow",
+ "affirmation",
+ "actionSteps"
+ ],
+ "type": "object"
+}post_angel_numbers_daily1 field 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"
+}get_angel_numbers2 fields changedInput schema / properties / lang / descriptionPrevious 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."Input schema / properties / lang / enumPrevious value: -[
- "en",
- "tr",
- "de",
- "es",
- "hi",
- "pt",
- "fr",
- "ru"
-]New value: +[
+ "en",
+ "tr",
+ "de",
+ "es",
+ "hi",
+ "pt",
+ "fr",
+ "ru",
+ "zh-Hans",
+ "zh-Hant"
+]get_angel_numbers_lookup2 fields changedInput schema / properties / lang / descriptionPrevious 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."Input schema / properties / lang / enumPrevious value: -[
- "en",
- "tr",
- "de",
- "es",
- "hi",
- "pt",
- "fr",
- "ru"
-]New value: +[
+ "en",
+ "tr",
+ "de",
+ "es",
+ "hi",
+ "pt",
+ "fr",
+ "ru",
+ "zh-Hans",
+ "zh-Hant"
+]get_angel_numbers_number2 fields changedInput schema / properties / lang / descriptionPrevious 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."Input schema / properties / lang / enumPrevious value: -[
- "en",
- "tr",
- "de",
- "es",
- "hi",
- "pt",
- "fr",
- "ru"
-]New value: +[
+ "en",
+ "tr",
+ "de",
+ "es",
+ "hi",
+ "pt",
+ "fr",
+ "ru",
+ "zh-Hans",
+ "zh-Hant"
+]post_angel_numbers_daily2 fields changedInput schema / properties / lang / descriptionPrevious 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."Input schema / properties / lang / enumPrevious value: -[
- "en",
- "tr",
- "de",
- "es",
- "hi",
- "pt",
- "fr",
- "ru"
-]New value: +[
+ "en",
+ "tr",
+ "de",
+ "es",
+ "hi",
+ "pt",
+ "fr",
+ "ru",
+ "zh-Hans",
+ "zh-Hant"
+]get_angel_numbers2 fields changedInput schema / examplesAdded value: +[
+ {}
+]Input schema / properties / compact / descriptionPrevious 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."get_angel_numbers_lookup2 fields changedInput schema / examplesAdded value: +[
+ {
+ "number": "1234"
+ }
+]Input schema / properties / compact / descriptionPrevious 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."get_angel_numbers_number2 fields changedInput schema / examplesAdded value: +[
+ {
+ "number": "444"
+ }
+]Input schema / properties / compact / descriptionPrevious 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."post_angel_numbers_daily2 fields changedInput schema / examplesAdded value: +[
+ {}
+]Input schema / properties / compact / descriptionPrevious 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."get_angel_numbers1 field changedInput schema / properties / offset / typePrevious value: -"integer"New value: +[
+ "integer",
+ "null"
+]get_angel_numbers1 field changedInput schema / properties / compact / descriptionPrevious 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."get_angel_numbers_lookup1 field changedInput schema / properties / compact / descriptionPrevious 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."get_angel_numbers_number1 field changedInput schema / properties / compact / descriptionPrevious 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."post_angel_numbers_daily1 field changedInput schema / properties / compact / descriptionPrevious 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."get_angel_numbers1 field changedInput schema / properties / compactAdded 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"
+}get_angel_numbers_lookup1 field changedInput schema / properties / compactAdded 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"
+}get_angel_numbers_number1 field changedInput schema / properties / compactAdded 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"
+}post_angel_numbers_daily1 field changedInput schema / properties / compactAdded 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"
+}get_angel_numbersget_angel_numbers_numberget_angel_numbers_numbersget_angel_numbers_numbers_numberget_angel_numbers_lookupget_angel_numbers_numbersget_angel_numbers_numbers_numberpost_angel_numbers_dailyLife Path, Expression, karmic debt and Chaldean numerology readings for AI agents.
Daily horoscopes for AI agents: one playful forecast per zodiac sign, every day.
Kua numbers, Eight Mansions, Flying Star charts and annual afflictions for AI agents.
I Ching hexagram casts, 64 hexagram meanings and changing lines for AI agents.
Add one secure layer between your agents and this server.
