Skip to main content
Glama
astroway

astroway-mcp

Official

Balance (chaldean)

numerology_chaldean_balance
Read-onlyIdempotent

Compute the Chaldean Balance number from the initials of each part of your full name.

Instructions

Calculate the Balance number from initials of each part of the full name. Numerology — Chaldean system.

[Group: Numerology — Chaldean]

Example request body: {"name":"John Smith","date":"1990-05-15"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate YYYY-MM-DD
latitudeNoLatitude (some date-only endpoints accept location)
longitudeNoLongitude
timezoneOffsetNoUTC offset in hours
Behavior3/5

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

Annotations already declare this as read-only and idempotent. The description adds that it calculates from initials, which is consistent but does not provide significant additional behavioral context beyond the input schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loaded with the purpose. However, the example contains an extraneous parameter not in the schema, which is inaccurate and misleading.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description does not explain how the name is provided (missing from schema), nor does it describe the return value. For a tool with 4 parameters and no output schema, this is critically incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

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

The description states the tool uses initials from the full name, yet the input schema does not include any 'name' parameter. The example includes 'name' which is not in the schema, creating confusion. Schema coverage is 100% but the description contradicts the schema.

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 it calculates the Balance number using initials from the full name, specifying the Numerology Chaldean system. This distinguishes it from other Chaldean numerology tools like life_path or expression.

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

Usage Guidelines3/5

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

An example request body with name and date is provided, implying use when these are available. However, no explicit guidance on when to use this versus sibling tools (e.g., other Chaldean numerology calculators) is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server