Skip to main content
Glama
Sign In

Asterwise

by com.asterwise
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/

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>",
      "date": "<date>"
    },
    "name": "asterwise_get_chaldean_numerology"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format.
nameYesPerson's full name as commonly written; its 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

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. 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."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the INPUT CONTRACT states name/date are forwarded as-is with no local validation, and it points to the output/error contract URL. It stops short of describing return shape, but the output schema covers that.

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-loads the one-line purpose, then uses labeled blocks (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) that each carry routing or contract value rather than filler. Slightly more scaffolding than strictly necessary for a 3-parameter tool, but nothing is wasted.

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 no prose. Between the purpose line, the explicit sibling routing, and the input contract, an agent has everything required to select and invoke the tool correctly.

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 format, name handling, and the response_format enum. The description adds nothing parameter-specific beyond restating that name and date are the inputs, so the baseline 3 applies.

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 (reduces), the resources (a name and birth date), the method (Chaldean letter-value system), and the return content (name, birth, combined compound analyses with themes and keywords). It explicitly names the siblings it must not be confused with, so an agent can distinguish it without opening any schema.

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 and DO NOT CONFUSE WITH blocks give explicit when-to-use routing: standalone before-hook, an AFTER handoff to asterwise_get_numerology_profile, and two named alternatives with the exact distinguishing factor for each (Pythagorean stack vs Chaldean compounds, magic-square digit placement vs name reduction).

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