Asterwise

Mobile Number Check

asterwise_check_mobile_number

Read-onlyIdempotent

Digit-strips a mobile string (keeping country code digits), reduces it with the owner's name and birth date, and returns harmonic scoring plus interpretive copy.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — anchor Life Path before judging the line. AFTER: None.

INPUT CONTRACT: Formatting noise is ignored; only digits contribute. Country code digits are included in the reduction sum.

DO NOT CONFUSE WITH: asterwise_check_vehicle_number — plate digit rules, not SIM numbering. asterwise_get_business_name_analysis — letter Expression scan, not phone roots.

Full output and error contract: https://docs.asterwise.com/mcp/tools/check-mobile-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.
`mobile_number`	Yes	Mobile number to analyse; digits only, country code optional.
`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.

Changed4 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 / mobile_number / description

Added value: +"Mobile number to analyse; digits only, country code optional."

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: -[
-  "mobile_number",
-  "name",
-  "date",
-  "response_format"
-]New value: +[
+  "mobile_number",
+  "name",
+  "date"
+]

First observedApr 22, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds meaningful behavior beyond that: formatting noise is ignored, only digits contribute, country code digits are included in the reduction sum, and the output is harmonic scoring plus interpretive copy. A doc link supplies the full output/error contract.

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 compact and uses labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE) to front-load the most important routing and input information. Every sentence earns its place, and the docs link is an appropriate terminal reference.

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 read-only numerology analysis tool, the description covers what the tool does, how inputs are normalized, which sibling to use before it, which siblings to avoid confusing it with, and where to find the full contract. An output schema and annotations handle return shape and side-effect safety.

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 coverage is 100%, so the baseline is 3. The description adds value by clarifying input normalization and reduction semantics: formatting noise is ignored, only digits contribute, and country code digits are included in the reduction sum—details not inferable from the schema alone.

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 transformation: digit-stripping a mobile string, reducing it with the owner's name and birth date, and returning harmonic scoring plus interpretive copy. It also names two sibling tools it should not be confused with, making its domain distinct.

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?

A WORKFLOW section recommends anchoring with asterwise_get_numerology_profile before judging the line, and the DO NOT CONFUSE WITH section explicitly excludes vehicle plate and business-name analysis by contrasting their rules. This gives an agent clear routing between this tool and near-neighbor siblings.

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?