Skip to main content
Glama

Numerology MCP Server by RoxyAPI

by com.roxyapi

Compound number meaning - Cheiro Chaldean interpretation 10 to 52

get_numerology_compound_number
Read-only

Get the classical Chaldean interpretation of a compound number (also called a fadic number) from 10 to 52, as defined by Cheiro in the Book of Numbers. Compound numbers are the unreduced two-digit numbers that reveal the hidden influence behind a name or date, beyond the single-digit root. Each returns its symbolic title (such as The Wheel of Fortune for 10, The Star of the Magi for 17, or The Crown of the Magi for 21), its nature (fortunate, unfortunate, or mixed), and a full interpretation. Numbers 33 to 52 share the meaning of a lower number in their series, returned with a sameAs pointer. Perfect for Chaldean numerology references, compound number lookups, and AI numerology tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse 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
numberYesCompound number from 10 to 52.
compactNoSet 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.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the tool read-only, so the description does not need to repeat that. It instead discloses substantive behavior: each result includes a symbolic title, nature, and full interpretation, and numbers 33 to 52 return a sameAs pointer to a lower number. This is useful behavioral detail beyond the annotations.

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 information-dense and front-loaded with the core lookup behavior, then return structure, then edge-case behavior. The final 'Perfect for' sentence is slightly promotional but does not waste much space.

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?

There is no output schema, so the description takes on the responsibility of describing the returned fields, which it does clearly: symbolic title, nature, interpretation, and sameAs behavior. It also covers the number range, the Cheiro source, and the tool's role in numerology workflows. This makes the tool safe and expected for an agent to call 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?

The input schema's descriptions already cover 100% of the parameters, including number, lang, and compact. The description adds no new parameter semantics beyond illustrative examples like The Wheel of Fortune for 10, so it is neither detrimental nor heavily compensatory.

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 opens with a specific verb and resource: 'Get the classical Chaldean interpretation of a compound number ... from 10 to 52'. It also sets clear scope by explaining compound numbers as unreduced two-digit numbers that go beyond the single-digit root, which differentiates it from ordinary numerology lookups and the sibling get_numerology_meanings_number.

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 closing 'Perfect for Chaldean numerology references, compound number lookups, and AI numerology tools' gives clear usage context. However, it does not explicitly tell the agent when not to use this tool or name an alternative for single-digit number meanings, so it falls short of full when/when-not 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 toolsInspect
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