Skip to main content
Glama
Sign In

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

Crystal Lookup

asterwise_get_crystal
Read-onlyIdempotent

Lookup a specific crystal by slug or name (case-insensitive). Returns full detail including dual Vedic/Western planetary assignments, all healing properties, and any safety cautions.

WORKFLOW: BEFORE: None — standalone or after asterwise_get_gemstone_recommendations. AFTER: None.

INPUT CONTRACT: name: Crystal slug or display name. Examples: 'amethyst', 'blue-sapphire', 'Cat's Eye Chrysoberyl'

DO NOT CONFUSE WITH: asterwise_get_crystals — full 54-crystal catalogue. asterwise_get_crystal_by_planet — all crystals for a Vedic planet. asterwise_get_gemstone_recommendations — natal chart-based gem recommendations (house lordship rules), different from this database.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCrystal slug or display name, e.g. 'amethyst', 'blue-sapphire', 'Cat's Eye Chrysoberyl'.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Person's full name as commonly written; letters are converted to numerology values."New value: +"Crystal slug or display name, e.g. 'amethyst', 'blue-sapphire', 'Cat's Eye Chrysoberyl'."
  2. Changed2 schema fields changed
    • 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."
  3. Changed2 schema fields changed
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "response_format"
-]New value: +[
+  "name"
+]
  4. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, covering the safety profile. The description adds case-insensitive matching and flags that the payload carries dual planetary assignments, healing properties, and safety cautions, but a docs link is deferred to for the error contract rather than stating it inline.

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?

Front-loaded purpose followed by clearly labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) that make scanning easy. The 'BEFORE: None — AFTER: None' line is somewhat formulaic filler, slightly diluting efficiency.

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?

An output schema exists, so return values need not be enumerated, yet the description still summarizes the payload and links an error contract, leaving few gaps. Given a 2-parameter read-only tool, this is complete enough for correct invocation.

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%, so both parameters (name, response_format) are already documented, and the description's name examples ('amethyst', 'blue-sapphire', "Cat's Eye Chrysoberyl") merely duplicate the schema. Baseline 3 applies since the schema does the heavy lifting and the description adds no new parameter meaning.

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?

States a specific verb+resource ('Lookup a specific crystal') with matching rules (slug or name, case-insensitive) and the depth of detail returned. The 'DO NOT CONFUSE WITH' block explicitly separates it from get_crystals (catalogue), get_crystal_by_planet, and get_gemstone_recommendations, so an agent can disambiguate without opening schemas.

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?

Gives a workflow slot ('standalone or after asterwise_get_gemstone_recommendations') and names three alternatives with their distinct scopes. It stops short of full when-not guidance (e.g., no explicit trigger distinguishing name lookup from the catalogue, only the scope distinction).

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

All Asterwise toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources