Asterwise

Balance Number

asterwise_get_balance_number

Read-onlyIdempotent

Calculates the Balance number from the first letter of each name part, using Pythagorean values. A three-part name yields three initials summed and reduced. The Balance number describes how a person handles emotional crises and unresolved inner conflict.

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

INPUT CONTRACT: name — Full legal name as used at birth. The first letter of each space-separated part contributes one value. Example: 'Arjun Mehta' → A(1) + M(4) = 5 Example: 'James Earl Carter' → J(1) + E(5) + C(3) = 9

DO NOT CONFUSE WITH: asterwise_get_expression_number — uses all letters, not just initials. asterwise_get_karmic_lessons — identifies absent digits across all letters.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-balance-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": {
      "name": "<name>"
    },
    "name": "asterwise_get_balance_number"
  }
}

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 carry the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description is not obligated to restate it. It does add genuine behavioral context beyond the annotations: the deterministic reduction algorithm, the meaning of the returned number, and a pointer to the full output/error contract. It stops short of disclosing failure modes inline (e.g., what happens with a single-part or empty name), so a 4 rather than 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.

Conciseness4/5

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

Labelled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE) front-load the essential constraint and the examples are concrete. There is minor redundancy between the prose sentence 'A three-part name yields three initials summed and reduced' and the three-part example that follows it, and the 'BEFORE: None / AFTER: None' block is slightly padded, but nothing is wasted enough to drop below 4.

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 described here. For a two-parameter, read-only calculation tool, the description supplies the computation method, the input contract with examples, sibling disambiguation, and an external contract link — everything an agent needs to select and invoke it correctly.

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. The INPUT CONTRACT exceeds the schema by adding a worked semantic example for the name parameter ('Arjun Mehta' → A(1) + M(4) = 5, and a three-part case), which disambiguates which letters are actually used. It adds little for response_format beyond what the schema enum already documents, keeping it from a 5.

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 ('Calculates the Balance number from the first letter of each name part') and then adds the method (Pythagorean values, initials summed and reduced) so the agent knows exactly what computation is performed. The explicit DO NOT CONFUSE section names the two nearest siblings and the rule that separates them (all letters vs. initials; absent digits), which no other sibling could claim.

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?

The WORKFLOW block declares 'BEFORE: None — standalone' and 'AFTER: None', removing any sequencing ambiguity. It then explicitly excludes asterwise_get_expression_number and asterwise_get_karmic_lessons with the distinguishing condition for each, so the agent has both when-to-use and when-not-to-use 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?