Asterwise

Crystal Recommendations

asterwise_get_crystal_recommendations

Read-onlyIdempotent

Recommends crystals based on zodiac sign, chakra, or intention keyword. At least one filter is required. Returns crystals that match the most criteria first.

WORKFLOW: BEFORE: None — standalone for consumer apps. AFTER: asterwise_get_crystal — get full detail on any recommended crystal.

INPUT CONTRACT: At least one of: zodiac_sign, chakra, intention must be provided. zodiac_sign (optional): English zodiac sign, e.g. 'Taurus', 'Scorpio'. chakra (optional): One of Root, Sacral, Solar Plexus, Heart, Throat, Third Eye, Crown. intention (optional): Keyword string, e.g. 'protection', 'abundance', 'love'. limit (optional int, default 5, max 20): Maximum results to return.

DO NOT CONFUSE WITH: asterwise_get_crystal_by_planet — Vedic planet filter only. asterwise_get_gemstone_recommendations — natal chart house-lordship gem prescription with contraindications.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return.
`chakra`	No	Chakra to focus on, e.g. 'heart' or 'third eye'.
`intention`	No	Purpose for the recommendation, e.g. 'protection', 'focus', 'love'.
`zodiac_sign`	No	Zodiac sign, e.g. 'Leo'.
`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 / chakra / description

Added value: +"Chakra to focus on, e.g. 'heart' or 'third eye'."

addedInput schema / properties / intention / description

Added value: +"Purpose for the recommendation, e.g. 'protection', 'focus', 'love'."

addedInput schema / properties / limit / description

Added value: +"Maximum number of results to return."

addedInput schema / properties / response_format / description

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

addedInput schema / properties / zodiac_sign / description
```
Added value: +"Zodiac sign, e.g. 'Leo'."
```

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- removedInput schema / required
```
Removed value: -[
-  "response_format"
-]
```
AddedMay 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond annotations: results are sorted by how many criteria match, at least one filter is required, and the follow-up workflow points to asterwise_get_crystal. It does not mention rate limits or auth, but those are not critical for this simple read-only tool.

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 with clear sections for workflow, input contract, and disambiguation. It is front-loaded with the core purpose and retains useful detail. Minor redundancy exists because 'at least one filter is required' appears in both the opening paragraph and the input contract, but the overall structure is efficient.

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 output schema, annotations, and full schema parameter coverage, the description is complete enough for an agent to select and invoke the tool correctly. It covers required input conditions, sorting behavior, follow-up workflow, sibling disambiguation, and points to a full output/error contract. Nothing essential is missing.

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, but the description adds real value beyond the schema: it specifies that at least one of three filters is required, enumerates valid chakra values, gives examples for zodiac_sign and intention, and adds a max of 20 for limit that the schema does not state. The response_format parameter is left entirely to the schema, but that is acceptable given 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 states a specific action and resource: it recommends crystals based on zodiac sign, chakra, or intention keyword. It also distinguishes itself from directly related siblings such as asterwise_get_crystal_by_planet and asterwise_get_gemstone_recommendations in the 'DO NOT CONFUSE WITH' section.

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 description gives clear when-to-use context with the standalone consumer-app workflow, and explicitly lists alternatives to avoid confusing with. It also states the required input contract, making it clear that at least one of zodiac_sign, chakra, or intention must be supplied.

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?