Skip to main content
Glama

Numerology MCP Server by RoxyAPI

by com.roxyapi

Get daily numerology number - Number of the Day with interpretation

post_numerology_daily
Read-only

Receive a daily numerology number (1-9, 11, 22, 33) for guidance and reflection. Uses seeded randomness so the same seed gets the same number on the same date, perfect for "Number of the Day" features in numerology apps, wellness platforms, and daily guidance tools. Returns the number with full interpretation including archetype, keywords, strengths, challenges, career, relationships, and spiritual insights. Ideal for daily push notifications, morning briefings, and personalized numerology experiences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.
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
seedNoOptional seed for reproducible readings. Same seed + same date = same number every time. Pass any unique identifier (userId, email hash, session token). Omit for anonymous daily readings.
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

A3.9/5.0
Behavior4/5

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

The description adds meaningful behavioral detail beyond the readOnly annotation: seeded randomness ensures the same seed plus date produces the same result. It also discloses that the response includes interpretation fields such as archetype, keywords, strengths, challenges, career, relationships, and spiritual insights. 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.

Conciseness4/5

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

The description is concise and front-loaded: it states purpose, reproducibility, and return value quickly. The 'perfect for' and 'ideal for' phrases add context but are slightly promotional.

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?

With no output schema, the description usefully lists inside categories returned. Optional params are thoroughly handled in the schema, and the readOnlyFeature remains baked by annotations. The description is complete enough for correct invocation.

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 four parameters are already fully documented in the schema, so the description does not need to repeat them. The description reinforces the seed parameter's purpose, but adds little beyond the schema's own coverage.

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 the resource is a daily numerology number (1-9, 11, 22, 33) and that it returns a full interpretation. It is distinct enough to identify the tool's main purpose, though it does not explicitly differentiate from any of the many sibling numerology tools.

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 provides strong application context: 'Number of the Day' features, wellness platforms, daily push notifications, and morning briefings. It also explains when deterministic seeded readings are useful. However, it does not explicitly say when not to use this tool or which sibling tool to choose instead.

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