Numerology MCP Server by RoxyAPI

Generate Complete Numerology Chart - Full profile analysis

post_numerology_chart

Read-only

Generate a comprehensive numerology chart combining all major calculations: Life Path, Expression, Soul Urge, Personality, Birth Day, Maturity, Karmic Lessons, Karmic Debt, and Personal Year. This single endpoint provides everything needed for a full numerology reading. Returns detailed interpretations for all numbers, karmic analysis, yearly forecast, and holistic summary. Perfect for numerology apps, complete reading services, birth chart generators, and comprehensive analysis tools. Save multiple API calls by getting the full chart in one request. Ideal for generating PDF reports or detailed user profiles.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	Yes	Birth day (1-31)
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`year`	Yes	Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).
`month`	Yes	Birth month (1-12)
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
`fullName`	Yes	Full birth name as it appears on the birth certificate. Used for all letter-based Pythagorean numerology calculations including Expression, Soul Urge, Personality, and Karmic Lessons.
`currentYear`	No	Year for Personal Year calculation (defaults to current year)

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate safety. It adds behavioral context beyond those annotations by revealing that one call returns an aggregated bundle containing interpretations, karmic analysis, yearly forecast, and a holistic summary, plus the compact-mode cost savings. No contradiction with annotations.

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 first sentence succeeds in front-loading the main purpose. However, later sentences include promotional filler like 'Perfect for numerology apps, complete reading services...' and 'Ideal for generating PDF reports...' that repeat the single-endpoint value and don't sharpen the agent's ability to call the tool correctly.

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?

Despite having no output schema, the description conveys what a caller should expect: detailed interpretations, karmic analysis, yearly forecast, and summary. Input requirements are fully covered by schema plus examples. It could be stronger by sketching the exact JSON output shape, but for the purpose of selecting and calling the tool, it is largely complete.

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?

All 7 parameters are described in the schema with 100% coverage, so the description doesn't need to repeat parameter details. It correctly implies that birth data and fullName are required inputs, but it doesn't add any parameter-specific meaning beyond 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 the action ('Generate'), the resource ('a comprehensive numerology chart'), and exactly which calculations are included. The phrase 'single endpoint provides everything needed for a full numerology reading' distinguishes it from the many individual numerology endpoints in the sibling list.

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 explicitly tells you when to use this tool: when you need a complete chart and want to avoid multiple API calls. It doesn't explicitly name individual sibling endpoints as alternatives for narrower queries, so it stops short of full 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 Numerology MCP Server by RoxyAPI tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Each tool targets a specific numerology calculation or lookup, and descriptions make the intended resource clear. A few tools have possible overlap—such as post_numerology_daily vs. post_numerology_personal_day and post_numerology_business_name vs. post_numerology_chaldean—but the distinctions are recoverable from context.

Naming Consistency5/5

Tool names follow a consistent pattern: get_numerology_* for lookups and post_numerology_* for calculations, all using snake_case. This makes both the operation type and the resource target predictable across the whole server.

Tool Count3/5

20 tools is on the heavy side for a single numerology server, and some tools such as post_numerology_chart and get_numerology_meanings_number overlap with or aggregate the results of individual calculation endpoints. The count is not unreasonable for a broad numerology API, but it stretches into a large surface area for an agent to navigate.

Completeness5/5

The server covers the major numerology surface well: core core numbers, personal cycles, karmic calculations, compatibility, Chaldean/Pythagorean variants, business name analysis, and a comprehensive chart endpoint. Only very niche numerology features are absent, so the tool set can serve end-to-end yoga use cases without obvious dead ends.

Resources

Need Help?