Skip to main content
Glama

Crystals MCP Server by RoxyAPI

by com.roxyapi

List All Crystals

get_crystals
Read-only

Retrieve healing crystals and gemstones with pagination. Supports optional filtering by chakra, zodiac sign, element, color, or planet. Returns minimal summary fields per crystal. Use the detail endpoint for full healing properties. Perfect for building crystal explorer apps, healing stone guides, and personalized crystal recommendation engines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse 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
colorNoFilter by crystal color (partial match, case-insensitive). E.g., "pink", "green", "blue", "purple". Use GET /colors for valid values.
limitNoMaximum items to return per page. Range: 1-100, default 20.
chakraNoFilter by chakra association, case-insensitive. Valid values: Root, Sacral, Solar Plexus, Heart, Throat, Third Eye, Crown.
offsetNoNumber of items to skip for pagination. Default 0.
planetNoFilter by planetary association (partial match, case-insensitive). E.g., "Venus", "Moon", "Jupiter". Use GET /planets for valid values.
zodiacNoFilter by zodiac sign, case-insensitive. Valid values: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces.
compactNoSet 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.
elementNoFilter by elemental association, case-insensitive. Valid values: Earth, Water, Fire, Air, Storm.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context by stating the API returns only minimal summary fields and that full healing properties require a separate detail endpoint, plus it notes pagination support.

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 front-loaded with the core action and key behavior, followed by a useful pointer to the detail endpoint. The final 'Perfect for...' sentence is somewhat promotional but still provides use-case context, so it is not excessive.

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?

With nine optional parameters and no output schema, the description gives a clear enough picture of expected behavior: paginated list, optional filters, compact summary responses available via schema, and a detail endpoint for richer data. It falls slightly short by not explicitly describing response shape or the exact detail endpoint name, but the description is otherwise functionally complete.

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?

Since schema description coverage is 100%, the baseline is 3; the schema already explains each parameter. The description adds context grouping filters like chakra, zodiac, element, color, and planet, but does not meaningfully explain further semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves crystals with pagination and optional filters, and the title reinforces a list-all resource. However, it does not explicitly differentiate itself from sibling tools like get_crystals_search or get_crystals_random; it only references a generic 'detail endpoint'.

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 gives clear context: it is for building crystal explorers, guides, and recommendation engines, and tells the agent to use the detail endpoint when full healing properties are needed. However, it does not explicitly say when to prefer alternatives like the search, random, or specific filter endpoints.

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

All Crystals MCP Server by RoxyAPI toolsInspect
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

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is overlap between get_crystals with filters and the dedicated endpoints for chakra, element, zodiac, and birthstone. The descriptive names and detailed explanations help agents choose correctly, though mis-selection is possible.

Naming Consistency4/5

All tools follow the get_crystals_<suffix> pattern except post_crystals_daily, which uses a post verb for a read operation. This minor deviation, along with the slightly awkward get_crystals_id and get_crystals_pairings_id, keeps the naming consistent overall.

Tool Count5/5

With 12 tools, the server is well-scoped for a crystal reference API. It covers listing, detail, search, random, daily, pairings, and filter-specific endpoints, each earning its place without feeling redundant or excessive.

Completeness4/5

The API provides comprehensive lookup coverage for crystals, including list, detail, search, random, daily, pairings, and filter/reference endpoints. The lack of dedicated endpoints for color and planet filters (only reference lists) is a minor gap, but the generic filter covers these use cases.

Resources