Asterwise

Maturity Number

asterwise_get_maturity_number

Read-onlyIdempotent

Calculates the Maturity number as the sum of Life Path and Expression numbers, reduced to a single digit or master number. Represents the underlying wish or true desire that becomes conscious around age 35 and fully emerges by midlife.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — confirm Life Path and Expression before interpreting their sum. AFTER: None.

INPUT CONTRACT: name — Full legal name as used at birth. Example: 'Arjun Mehta' date — Birth date in YYYY-MM-DD format. Example: '1985-11-12'

DO NOT CONFUSE WITH: asterwise_get_numerology_profile — returns maturity_number as part of the full profile. asterwise_get_personal_cycles — temporal cycles that change annually, not a fixed number.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-maturity-number/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD format. Defaults to today when omitted.
`name`	Yes	Person's full name as commonly written; letters are converted to numerology values.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 5, 2026

addedInput schema / properties / date / description

Added value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."

addedInput schema / properties / name / description

Added value: +"Person's full name as commonly written; letters are converted to numerology values."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "name",
-  "date",
-  "response_format"
-]New value: +[
+  "name",
+  "date"
+]

AddedMay 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the bar is lower; the description adds value by disclosing the calculation method (sum and master-number reduction) and the interpretive meaning of the result. It also links to the full output and error contract. It does not contradict any annotation, though it could have clarified how borderline master-number cases are handled for extra transparency.

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 core computation is front-loaded in the first sentence, and the WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE sections make the content scannable. Some redundancy with the schema's parameter descriptions exists, but the examples and workflow notes justify most of the length.

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?

For a deterministic read-only calculation with an output schema, the definition covers the formula, prerequisite workflow, alternatives, input contract, examples, and a link to the full output/error contract. No essential selection or invocation information is missing; return-value details are already supplied by the output schema.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds useful semantic value by specifying name as 'Full legal name as used at birth', giving concrete examples, and framing date as the birth date in YYYY-MM-DD format. This goes slightly beyond the schema's own descriptions without being exhaustive about response_format, which the schema already covers.

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 — 'Calculates the Maturity number' — and gives the exact derivation: sum of Life Path and Expression numbers reduced to a single digit or master number. The 'DO NOT CONFUSE WITH' section explicitly separates it from asterwise_get_numerology_profile and asterwise_get_personal_cycles, so it is unambiguous among the sibling tools.

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

Usage Guidelines5/5

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

The WORKFLOW block states a concrete prerequisite and a terminal state: 'BEFORE: RECOMMENDED — asterwise_get_numerology_profile' and 'AFTER: None'. The DO NOT CONFUSE WITH block names the alternatives and the exact conditions for preferring them, which is exactly the kind of routing guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asterwise 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

Disambiguation3/5

Many tools are well-differentiated by explicit 'DO NOT CONFUSE WITH' notes, but the sheer number of near-neighbor pairs (e.g., crystal vs gemstone recommendations, natal chart variants, dasha systems, compatibility systems, tarot draw variants) creates real selection risk. The descriptions mitigate overlap, but an agent browsing 103 tools will struggle to pick the right one.

Naming Consistency5/5

Every tool follows the asterwise_get_* or asterwise_draw_* prefix convention with a clear noun phrase (e.g., asterwise_get_natal_chart, asterwise_draw_tarot_cards). The two verbs 'get' and 'draw' are semantically appropriate, and there are no camelCase or mixed-style names.

Tool Count1/5

103 tools is far beyond a manageable MCP surface. While the domain is broad (Vedic astrology, Western astrology, numerology, tarot, crystals, dream symbols), the server bundles multiple distinct domains into one namespace, making it nearly impossible for an agent to discover the right tool efficiently.

Completeness4/5

The surface is impressively comprehensive across astrology, numerology, tarot, and remedies, with deep coverage of dasha systems, compatibility frameworks, and chart types. Minor gaps exist (e.g., no tarot interpretation endpoint, no batch operations, no update/delete since it's read-only data), but for a reference/prediction API the coverage is strong.

Resources

Need Help?