Crystals MCP Server by RoxyAPI

Get crystal by id - Crystal healing properties API

get_crystals_id

Read-only

Get complete healing properties and metaphysical data for a specific crystal or gemstone. Returns spiritual, emotional, and physical healing interpretations along with chakra associations, zodiac connections, elemental properties, and crystal pairing recommendations. Authoritative interpretations covering all major healing crystals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	URL-safe crystal identifier, case-insensitive (e.g., "amethyst", "Amethyst", "rose-quartz" all resolve). Must match an entry in the database.
`lang`	No	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.	en
`compact`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`colors`	Yes
`planet`	Yes
`chakras`	Yes
`meaning`	Yes
`elements`	Yes
`hardness`	Yes
`imageUrl`	Yes
`keywords`	Yes
`pairsWith`	Yes
`birthMonth`	Yes
`affirmation`	Yes
`description`	Yes
`zodiacSigns`	Yes
`numericalVibration`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "affirmation": {
+      "type": "string"
+    },
+    "birthMonth": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "chakras": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "colors": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "description": {
+      "type": "string"
+    },
+    "elements": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "hardness": {
+      "type": "number"
+    },
+    "id": {
+      "type": "string"
+    },
+    "imageUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keywords": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "meaning": {
+      "properties": {
+        "emotional": {
+          "type": "string"
+        },
+        "physical": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "spiritual": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "spiritual",
+        "emotional",
+        "physical"
+      ],
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "numericalVibration": {
+      "type": "number"
+    },
+    "pairsWith": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "planet": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "zodiacSigns": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "name",
+    "id",
+    "imageUrl",
+    "description",
+    "meaning",
+    "chakras",
+    "zodiacSigns",
+    "planet",
+    "elements",
+    "colors",
+    "hardness",
+    "numericalVibration",
+    "keywords",
+    "birthMonth",
+    "affirmation",
+    "pairsWith"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

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"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "amethyst"
+  }
+]

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."

Changed1 schema field changedJul 22, 2026

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."

Changed1 schema field changedJul 22, 2026

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"
+}

First observedJul 8, 2026

TDQS

A3.5/5.0

Behavior3/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 covered. The description adds context about what content is returned (spiritual, emotional, physical healing interpretations, chakra, zodiac, elemental, pairings) but does not disclose non-obvious behaviors such as language fallback, compact response shape, or not-found behavior. No contradiction with annotations.

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 a compact three-sentence definition with the main action and resource front-loaded. The enumeration of returned categories is useful, but the final 'Authoritative interpretations covering all major healing crystals' is promotional filler rather than actionable guidance.

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 a rich input schema, full parameter coverage, explicit annotations, and an output schema present, the description does not need to explain return structure or safety. It adequately covers the common invocation path for a known crystal id, though it could be more complete by naming sibling alternatives for fuzzy or list-based lookups.

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%: the id parameter is documented with case-insensitivity, lang has an enum and fallback behavior, and compact describes its columnar shape and token savings. The description itself adds no parameter-level detail, so the 3 baseline is appropriate.

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 uses a specific verb ('Get') and names the resource ('a specific crystal or gemstone') while enumerating the returned data categories. It is clearly distinct from list-oriented siblings, though it does not explicitly contrast itself with get_crystals_search or get_crystals_pairings_id; the title's 'by id' supplies the missing differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for a specific crystal or gemstone' implies the caller should already know the crystal identifier, giving some usage context. However, there is no explicit statement of when to use this tool instead of the many sibling lookup tools, no exclusions, and no mention of when search or list endpoints would be preferable.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?