Asterwise

Karmic Lessons

asterwise_get_karmic_lessons

Read-onlyIdempotent

Identifies karmic lessons by scanning all letter values in the full name and finding which digits 1–9 are absent. Each missing digit represents an area where experience is thin and development is needed in this lifetime.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — see karmic lessons alongside all core numbers.

INPUT CONTRACT: name — Full legal name as used at birth. Example: 'Arjun Mehta' — scan all 10 letters for their Pythagorean digit values. Letters present: A=1, R=9, J=1, U=3, N=5, M=4, E=5, H=8, T=2, A=1 Digits present: {1,2,3,4,5,8,9} → Missing: {6,7}

DO NOT CONFUSE WITH: asterwise_get_balance_number — uses only first letters (initials), not all letters. asterwise_get_expression_number — reduces all letters to a single number; does not scan for absent digits.

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

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Full legal name as used at birth, all parts; its letters are converted to numerology values.
`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.

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / name / description

Previous value: -"Person's full name as commonly written; its letters are converted to numerology values."New value: +"Full legal name as used at birth, all parts; its letters are converted to numerology values."

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / name / description

Previous value: -"Person's full name as commonly written; letters are converted to numerology values."New value: +"Person's full name as commonly written; its letters are converted to numerology values."

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / name / description

Added value: +"Person's full name as commonly written; letters are converted to numerology values."

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: -[
-  "name",
-  "response_format"
-]New value: +[
+  "name"
+]
```
AddedMay 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint/idempotent/non-destructive, and the description adds real value beyond them: the actual algorithm, a worked example, and an input contract. It doesn't detail error/edge behavior beyond linking to a docs URL, so not a full 5, but the safety profile plus method is well disclosed.

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 purpose, then structured into WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH headings. The worked example is long but earns its place by demonstrating the algorithm; only minor trimming is possible.

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?

An output schema exists, so return values need not be explained, and the description still covers purpose, algorithm, workflow ordering, sibling disambiguation, and an error-contract pointer. 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds an INPUT CONTRACT section with a concrete worked example ('Arjun Mehta' → letters → missing {6,7}) that makes the 'name' parameter's expected form clearer than the schema alone.

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 ('Identifies karmic lessons by scanning all letter values...finding which digits 1–9 are absent') and goes further to explain the mechanism. It actively distinguishes itself from siblings with a 'DO NOT CONFUSE WITH' section naming balance_number and expression_number.

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 an explicit workflow (BEFORE: None — standalone; AFTER: asterwise_get_numerology_profile) and enumerates the sibling tools this should NOT be confused with, along with why. When-to-use and when-not-to-use are both 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?