Asterwise

Angel Number Today

asterwise_get_angel_number_today

Read-onlyIdempotent

Returns the angel number for today (UTC, or the caller's timezone) or for a given date. All digits of the date are summed and reduced to a single digit (1-9), then the triple sequence of that digit is returned (e.g. digit 9 → angel number 999).

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_angel_number_personal — for a personalised angel number from birth date.

INPUT CONTRACT: date (optional YYYY-MM-DD) or timezone (optional IANA, e.g. Asia/Kolkata); without either, today is the current UTC date. date overrides timezone.

DO NOT CONFUSE WITH: asterwise_get_angel_number — lookup for a specific number sequence by value. asterwise_get_angel_number_personal — personalised number from birth date Life Path.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "asterwise_get_angel_number_today"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	Date to compute the angel number for, YYYY-MM-DD. Overrides timezone. Omit for today.
`timezone`	No	IANA time zone whose current date counts as today, e.g. 'Asia/Kolkata'. Defaults to UTC; ignored when date is given.
`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 changedOct 8, 2026

addedInput schema / properties / date

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Date to compute the angel number for, YYYY-MM-DD. Overrides timezone. Omit for today."
+}

addedInput schema / properties / timezone

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "IANA time zone whose current date counts as today, e.g. 'Asia/Kolkata'. Defaults to UTC; ignored when date is given."
+}

Changed1 schema field changedSep 5, 2026

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"
```
- removedInput schema / required
```
Removed value: -[
-  "response_format"
-]
```
AddedMay 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context: the deterministic digit-sum-to-triple algorithm, the date-overrides-timezone precedence rule, and the UTC default. It does not cover rate limits or error behavior, but it defers those to the linked docs, which is acceptable.

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?

Front-loaded with the core purpose, then cleanly sectioned into WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH. The section labels are somewhat verbose and the algorithm sentence is dense, but every section carries information an agent needs to route and call the tool.

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?

With an output schema present, the description need not explain return values, and it covers everything else: purpose, algorithm, input precedence, default behavior, sibling routing, and a link to the full output/error contract. Nothing an agent needs to call it correctly is missing.

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 schema already documents date, timezone, and response_format including the 'overrides timezone' precedence. The description's INPUT CONTRACT largely restates this (date overrides timezone; UTC default), adding only the format example (Asia/Kolkata). Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ('Returns the angel number for today ... or for a given date') and even spells out the reduction algorithm so the agent knows exactly what the output represents. The 'DO NOT CONFUSE WITH' block distinguishes it from asterwise_get_angel_number and asterwise_get_angel_number_personal, so the agent can select it without opening sibling schemas.

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?

Explicit routing is provided: WORKFLOW AFTER points to asterwise_get_angel_number_personal, and the DO NOT CONFUSE WITH section names the two nearest alternatives with the exact condition that separates them (today's date vs. specific sequence vs. birth-date personalisation). When-to-use is fully covered.

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?