Skip to main content
Glama
astroway

astroway-mcp

Official

Personal Year (chaldean)

numerology_chaldean_personal_year
Read-onlyIdempotent

Calculate your Personal Year number for any calendar year using the Chaldean numerology system. Discover your 9-year cycle of personal evolution.

Instructions

Calculate the Personal Year number for a given calendar year — 9-year cycle of personal evolution. Numerology — Chaldean system.

[Group: Numerology — Chaldean]

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

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 readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about the 9-year cycle but does not discuss behavioral traits like error handling, output format, or the role of location parameters.

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 concise (two lines) but includes a confusing example request body that does not match the schema. The group tag is helpful, but the example wastes space and creates ambiguity.

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

Completeness2/5

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

The tool has 4 parameters and no output schema, with many siblings. The description lacks explanation of the output, the meaning of personal year number, and why location parameters are included. More context is needed for an agent to use it correctly.

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

Parameters2/5

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

Schema coverage is 100% but the description adds no meaning beyond schema. The example includes 'year' and 'name' parameters not present in the schema, which is misleading and contradicts the actual parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it calculates the Personal Year number for a given calendar year, specifying the 9-year cycle and Chaldean system. However, the example includes parameters (name, year) not in the schema, causing some confusion.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Among many sibling numerology personal_year tools (e.g., pythagorean, vedic), the description only implies 'Chaldean system', but does not clarify scenarios or exclusions.

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