Skip to main content
Glama

Crystals MCP Server by RoxyAPI

by com.roxyapi

Search crystals - Crystal search API

get_crystals_search
Read-only

Search for healing crystals by keyword or name. Matches against crystal names, healing keywords, descriptions, and spiritual/emotional/physical meaning fields. Returns summary data for each crystal. Use the /crystals/{id} detail endpoint for full healing properties. Useful for building crystal search bars, keyword-based recommendation features, and healing property lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query (2-50 characters). Matches against crystal names, keywords, descriptions, and meaning fields. Case-insensitive partial matching.
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
limitNoMaximum items to return per page. Range: 1-50, default 20.
offsetNoNumber of items to skip for pagination. Default 0.
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.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response 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."
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "q": "love"
+  }
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set 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."
  3. Changed1 schema field changed
    • changedInput schema / properties / offset / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  5. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds useful behavioral context beyond annotations, notably that results contain 'summary data' rather than full healing properties, and that matching spans 'names, healing keywords, descriptions, and spiritual/emotional/physical meaning fields.' This helps an agent set correct expectations about output scope 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 five short, purposeful sentences with the primary action front-loaded. Each sentence earns its place: what the tool does, what fields it matches, what it returns, when to use the detail endpoint, and recommended use cases. There is no filler or repetition of schema details.

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?

Given the 5-parameter schema with 100% coverage, read-only annotations, and no output schema, the description covers the essential decision points: what is searched, what is returned, when to use the detail endpoint, and typical use cases. The main omission is any mention of pagination or language fallback behavior, but those are already thoroughly documented in the input schema, so the description remains sufficient for correct invocation.

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 structured schema already documents q, lang, limit, offset, and compact thoroughly. The description still adds meaning by clarifying the q parameter's searchable domains with the more specific phrase 'spiritual/emotional/physical meaning fields' and by noting results are summaries, which helps interpret the q and limit parameters. This is above the baseline but not heavily compensated because the schema already carries most parameter detail.

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: 'Search for healing crystals by keyword or name.' It goes on to enumerate exactly which fields are matched, and explicitly distinguishes this tool from the detail endpoint by stating it 'Returns summary data' and directing users to the /crystals/{id} endpoint for full properties. This clearly separates it from the get_crystals_id and other sibling list tools.

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 names concrete use cases: 'building crystal search bars, keyword-based recommendation features, and healing property lookups.' It also provides an explicit alternative for full healing properties: 'Use the /crystals/{id} detail endpoint.' However, it does not address when to prefer sibling filter tools like get_crystals_chakra or get_crystals_element, so routing guidance is good but not exhaustive.

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

A3.9/5.0
Disambiguation3/5

The main get_crystals endpoint already supports filtering by chakra, element, and zodiac, making the dedicated filter endpoints partially redundant. However, each tool has a clearly named purpose, so an agent can usually pick the right one.

Naming Consistency4/5

Most tools follow a consistent get_crystals_<suffix> pattern, but post_crystals_daily breaks the verb convention, and suffix ordering is slightly inconsistent (e.g., pairings_id vs id).

Tool Count5/5

12 tools is well within the ideal range for a domain-specific read-only API. Each tool serves a distinct browsing, search, detail, filter, reference, or discovery function.

Completeness4/5

The surface covers listing, detail, search, filters, random, daily, pairings, and reference values. Minor gap: no direct tool for enumerating chakras/elements/zodiac signs, though those are small fixed sets handled by the main list.

Resources