Skip to main content
Glama

Digital Gemology: gem identification and gemstone properties

Gemstone properties

gem_properties
Read-onlyIdempotent

Everything Digital Gemology has on one gemstone: refractive index (both rays for doubly refractive stones), birefringence, dispersion, specific gravity, hardness, crystal system, critical angle, what a refractometer, polariscope and dichroscope show, its pleochroic colors and the lines and bands a hand spectroscope shows, with links to the free tools. For the seven stones our tools model the values are the tools' own; for the others they are published reference values, with their sources. Also which stone's ray-traced cut scores apply to it (cut_scores_from, cut_scores_url), or why it has none (cut_scores_note).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gemstone": "<gemstone>"
    },
    "name": "gem_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
gemstoneYesGemstone, as its slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gemstone / enum
      Previous value: -[
      -  "diamond",
      -  "moissanite",
      -  "cubic-zirconia",
      -  "ruby",
      -  "sapphire",
      -  "emerald",
      -  "amethyst"
      -]New value: +[
      +  "diamond",
      +  "moissanite",
      +  "cubic-zirconia",
      +  "ruby",
      +  "sapphire",
      +  "emerald",
      +  "amethyst",
      +  "aquamarine",
      +  "morganite",
      +  "tanzanite",
      +  "topaz",
      +  "tourmaline",
      +  "pyrope",
      +  "almandine",
      +  "spessartine",
      +  "grossular",
      +  "demantoid",
      +  "spinel",
      +  "peridot",
      +  "citrine",
      +  "quartz",
      +  "opal",
      +  "jadeite",
      +  "nephrite",
      +  "turquoise",
      +  "chrysoberyl",
      +  "alexandrite",
      +  "zircon",
      +  "kunzite",
      +  "iolite",
      +  "moonstone",
      +  "yag",
      +  "ggg",
      +  "strontium-titanate",
      +  "glass",
      +  "synthetic-rutile"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the description's real contribution is provenance: values are the tools' own for the seven modeled stones and published references (with sources) otherwise. It also explains the cut_scores_from/cut_scores_url fields and the cut_scores_note that explains their absence, which is behavior no annotation conveys.

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?

It is front-loaded with the core claim ('Everything Digital Gemology has on one gemstone') and every listed item corresponds to actual returned content, so the long enumeration earns its space. The first sentence is an unbroken run-on, which costs a point on readability.

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?

There is no output schema, so the description must carry the return contract, and it does: it enumerates the property groups, states data provenance and sourcing, and explains the cut-score fields including the case where none apply. Nothing an agent needs to interpret the response is missing.

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 coverage is 100% and the single parameter is a fully enumerated slug list with its own description, so the schema carries the semantic load. The description adds nothing about slug formatting or how to handle a stone outside the enum, which is the baseline-3 case.

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 names a specific resource and enumerates exactly what it returns (refractive index, birefringence, dispersion, specific gravity, hardness, crystal system, instrument readouts, pleochroism, spectroscope bands). It is clearly a static reference lookup by stone, distinct from identify_gem or compare_gemstones, though it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the tool to call once it already knows the stone and wants reference data. There is no explicit guidance on when to prefer identify_gem (stone unknown) or compare_gemstones (multi-stone comparison), leaving that routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.