Skip to main content
Glama

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

Chaldean Numerology

asterwise_get_chaldean_numerology
Read-onlyIdempotent

Reduces a name and birth date through the Chaldean letter-value system and returns name, birth, and combined compound analyses with themes and keywords.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — compare against Pythagorean cores if needed.

INPUT CONTRACT: name and date forwarded as-is; no local validation.

DO NOT CONFUSE WITH: asterwise_get_numerology_profile — Pythagorean Life Path / Expression stack, not Chaldean compounds. asterwise_get_lo_shu_grid — digit placement magic square, not Chaldean name reduction.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format.
nameYesPerson's full name as commonly written; letters are converted to numerology values.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Date in YYYY-MM-DD format. Defaults to today when omitted."New value: +"Date in YYYY-MM-DD format."
  2. Changed3 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."
    • 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."
  3. Changed2 schema fields changed
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "date",
-  "response_format"
-]New value: +[
+  "name",
+  "date"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description does not need to repeat these. It adds useful behavioral detail about returning name, birth, and combined compound analyses, and the 'no local validation' note clarifies input handling.

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?

The description is organized with clear sections for workflow, input contract, and exclusions. It is somewhat verbose but each section serves a distinct purpose and there is little redundant filler.

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

Completeness4/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 does not need to exhaustively list return fields. It summarizes the return content and provides a link to the full output and error contract, which is sufficient for context.

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% and the description adds extra context about inputs being forwarded as-is with no local validation. The roles of name, date, and response_format are fully explained in the schema, and the description reinforces them.

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?

The description clearly states the tool reduces a name and birth date using the Chaldean letter-value system and returns compound analyses. It also distinguishes itself from similar tools like asterwise_get_numerology_profile and asterwise_get_lo_shu_grid.

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

Usage Guidelines4/5

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

The description provides workflow context and explicitly warns not to confuse this tool with Pythagorean-based numerology or Lo Shu grid tools. It lacks an explicit 'use this when' statement, but the workflow and exclusions offer strong practical guidance.

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

All Asterwise toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources