Asterwise

Angel Number

asterwise_get_angel_number

Read-onlyIdempotent

Lookup the meaning of a specific angel number by its sequence. Supported: 000, 111–999 (single repeating digit), 911, 1010, 1111, 1122, 1212, 1234, 2222–9999 (double repeating digit).

WORKFLOW: BEFORE: None — standalone. AFTER: None.

INPUT CONTRACT: number: string — the angel number sequence to look up. Examples: '111', '444', '1111', '911'.

DO NOT CONFUSE WITH: asterwise_get_angel_number_today — today's collective daily angel number. asterwise_get_angel_number_personal — personal angel number from birth date. asterwise_get_number_meaning — Pythagorean numerology meaning for 1–9 and master numbers 11, 22, 33; different tradition.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-angel-number/

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": {
      "number": "<number>"
    },
    "name": "asterwise_get_angel_number"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes	Angel number sequence as seen, e.g. '111' or '1234'.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / number / description

Added value: +"Angel number sequence as seen, e.g. '111' or '1234'."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "number",
-  "response_format"
-]New value: +[
+  "number"
+]
```
AddedMay 3, 2026

TDQS

A4.7/5.0

Behavior4/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 the safety profile is covered. The description adds genuine behavioral context beyond that: the enumeration of valid sequence inputs and the standalone (no side-effect, no chaining) nature. It does not describe the failure mode for unsupported input, deferring that to an external URL, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-sentence purpose followed by clearly labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH). Every line carries information, and the only external pointer is a single trailing URL rather than inlined boilerplate.

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

Completeness5/5

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

For a two-parameter, output-schema-backed lookup tool, nothing an agent needs is missing: valid inputs, sibling disambiguation, workflow context, and format selection. Return values are left to the output schema, correctly avoiding duplication.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (both parameters documented, response_format has an enum), so the baseline is 3. The description goes beyond the schema by adding a validation contract - the explicit supported-value range - that the schema's brief property description omits, which materially helps an agent avoid invalid calls.

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

Purpose5/5

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

States a specific verb (lookup) and resource (angel number meaning) plus the exact supported sequence set, which lets an agent know the valid domain immediately. It then explicitly blocks confusion with three named sibling tools, each with a one-line distinction, so the tool is unambiguous against alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit BEFORE/AFTER workflow (standalone, no prerequisites or follow-ups) and a dedicated 'DO NOT CONFUSE WITH' section that routes the agent to get_angel_number_today, get_angel_number_personal, or get_number_meaning with the condition that selects each. This is textbook when/when-not/alternatives guidance.

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

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?