Numerology MCP Server by RoxyAPI

Calculate Personal Month - Monthly numerology forecast

post_numerology_personal_month

Read-only

Calculate your Personal Month number from birth month, day, and a target year and month. Personal Month reveals the specific theme and energy influencing each calendar month within your Personal Year cycle. Returns the monthly theme, practical focus guidance, and the parent Personal Year context. Perfect for monthly forecast features, push notification content, calendar integrations, editorial monthly columns, and life coaching tools.

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`	No	Target year for calculation (defaults to current year)
`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.
`targetMonth`	No	Target calendar month to forecast (1-12, defaults to current month)

TDQS

A4.1/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false, annotations already cover the safety profile. The description adds behavioral value by specifying what the tool returns: monthly theme, practical focus guidance, and the parent Personal Year context. It stops short of describing exact output structure, but the main non-obvious behavior is disclosed.

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 well-structured and front-loads the core calculation and output. The opening 'Perfect for...' sentence lists plausible use cases but is not essential for invocation. This is slightly longer than necessary but still focused and readable.

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?

For a tool with no output schema, the description provides useful outcome detail (theme, practical focus, parent Personal Year context) and parameter context (birth info plus target month/year). It could additionally specify exact result shape or fallback language behavior, but the given coverage is adequate given full schema param descriptions and annotations.

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?

Schema description coverage is 100%, so each parameter is already documented. The description reinforces the core inputs (birth month/day, target year/month) and clarifies the requested period, but it adds little beyond what the schema already provides. This matches the baseline for full schema coverage.

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 action ('Calculate your Personal Month number') and resource basis (birth month/day plus target year/month). It further clarifies the result's meaning—monthly theme and energy within the Personal Year cycle—which clearly distinguishes it from related daily/yearly 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 clearly targets monthly forecast use cases and explicitly ties the result to a target calendar month, making the appropriate context evident without ambiguity. It names several application scenarios but does not explicitly contrast with sibling tools like post_numerology_personal_day or post_numerology_personal_year.

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?