Asterwise

Numerology Compatibility

asterwise_get_numerology_compatibility

Read-onlyIdempotent

Compares two people on Pythagorean Life Path numbers derived from their names and birth dates and returns a score, tier label, narrative, strengths, challenges, and advice.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile per person — sanity-check Life Paths before comparing. AFTER: None.

INPUT CONTRACT: Four strings (two names, two dates) are passed through without local guards.

DO NOT CONFUSE WITH: asterwise_get_compatibility — sidereal koota scoring, not numerology integers. asterwise_get_numerology_profile — single-person profile, not dyad scoring.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`person1_date`	Yes	First person's date of birth, YYYY-MM-DD.
`person1_name`	Yes	First person's full name.
`person2_date`	Yes	Second person's date of birth, YYYY-MM-DD.
`person2_name`	Yes	Second person's full name.
`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.

Changed5 schema fields changedSep 5, 2026
- addedInput schema / properties / person1_date / description
```
Added value: +"First person's date of birth, YYYY-MM-DD."
```
- addedInput schema / properties / person1_name / description
```
Added value: +"First person's full name."
```
- addedInput schema / properties / person2_date / description
```
Added value: +"Second person's date of birth, YYYY-MM-DD."
```
- addedInput schema / properties / person2_name / description
```
Added value: +"Second person's full name."
```
- 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: -[
-  "person1_name",
-  "person1_date",
-  "person2_name",
-  "person2_date",
-  "response_format"
-]New value: +[
+  "person1_name",
+  "person1_date",
+  "person2_name",
+  "person2_date"
+]

First observedApr 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds meaningful behavioral context beyond annotations: the input contract warns that four strings are 'passed through without local guards,' and it enumerates the output components. These details help predict behavior without contradicting 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.

Conciseness5/5

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

The description is well-structured with clear sections: a dense main sentence, a concise workflow note, an input contract warning, explicit sibling disambiguation, and a documentation link. Every section serves a distinct purpose and there is no redundant filler or repetition of schema details.

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?

Given the rich output schema, full parameter coverage in the schema, and annotations that establish read-only/idempotent behavior, the description is complete. It adds the workflow prerequisite, the no-local-guards warning, sibling exclusions, and a pointer to the full output/error contract. An agent has everything needed to invoke this tool 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?

Schema description coverage is 100%, so the schema fully documents all five parameters including date format, name meaning, and response_format enum. The description adds little parameter-level meaning beyond noting that the four strings are passed through unguarded, which is a behavioral caveat rather than a semantic clarification. Baseline 3 is appropriate.

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 precise verb and resource: 'Compares two people on Pythagorean Life Path numbers derived from their names and birth dates' and lists the exact return elements. It also explicitly distinguishes itself from asterwise_get_compatibility and asterwise_get_numerology_profile, so an agent can confidently separate it from close siblings.

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 section explicitly recommends calling asterwise_get_numerology_profile per person beforehand for sanity-checking Life Paths. The DO NOT CONFUSE WITH section names two alternatives and the exact reasons they differ, giving clear when-to-use and when-not-to-use guidance. This is exemplary usage direction.

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?