Skip to main content
Glama

Digital Gemology: gem identification and gemstone properties

Absorption spectrum

absorption_spectrum
Read-onlyIdempotent

What a hand spectroscope shows for one gemstone: each absorption line and band with its position in nanometres, its cause (for example Cr3+ in ruby) and what it looks like, from Digital Gemology's Spectroscope or, for the stones it does not model, published references.

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": "absorption_spectrum"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description earns credit for adding provenance: data comes from Digital Gemology's Spectroscope, with published references used for stones the model does not cover. That tells the agent about coverage and fallback behavior, though it does not say how gaps or missing lines are signalled in the result.

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?

A single front-loaded sentence leads with the scope ('what a hand spectroscope shows for one gemstone') before layering the returned fields and data sources. It is dense with nested clauses but every element carries information; no filler sentences.

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?

For a one-parameter read-only lookup with no output schema, the description adequately conveys what the result contains (line positions, causes, visual appearance) and where the data originates. Only minor gaps remain, such as whether reference-sourced stones look different or how an absent feature is represented.

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% and the single gemstone parameter is a fully enumerated slug list, so the schema does the heavy lifting. The description only reinforces 'for one gemstone' and adds no enumeration detail, matching the baseline of 3 for high-coverage schemas.

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 states precisely what is returned for a single gemstone: each absorption line and band, its position in nanometres, its cause (e.g. Cr3+ in ruby), and its visual appearance. That payload granularity effectively separates it from gem_properties and compare_gemstones, though no sibling is named 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?

The framing 'What a hand spectroscope shows' implies the use case (matching an observed spectrum or explaining absorption features), but there is no explicit when-to-use, when-not, or pointer to gem_properties/identify_gem as alternatives. Usage is inferable rather than stated.

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.