Skip to main content
Glama

Digital Gemology: gemstone and diamond cut library

One cut in one gemstone

cut_in_gemstone
Read-onlyIdempotent

How one cut performs in one gemstone: its headline, eight measured scores against the T73 round brilliant in the same stone, and its pros and cons. For questions like 'is an oval a good cut for sapphire?'.

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": {
      "cut": "<cut>",
      "gemstone": "<gemstone>"
    },
    "name": "cut_in_gemstone"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutYesThe cut's slug or name.
gemstoneYesGemstone, as its slug. An alias stone (aquamarine, citrine, quartz, alexandrite) answers with the figures of the stone it shares optical constants with, and says so.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / gemstone / description
      Previous value: -"Gemstone, as its slug."New value: +"Gemstone, as its slug. An alias stone (aquamarine, citrine, quartz, alexandrite) answers with the figures of the stone it shares optical constants with, and says so."
    • 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",
      +  "topaz",
      +  "spinel",
      +  "demantoid",
      +  "zircon",
      +  "tourmaline",
      +  "peridot",
      +  "tanzanite",
      +  "yag",
      +  "pyrope",
      +  "almandine",
      +  "spessartine",
      +  "grossular",
      +  "chrysoberyl",
      +  "kunzite",
      +  "iolite",
      +  "morganite",
      +  "ggg",
      +  "strontium-titanate",
      +  "synthetic-rutile",
      +  "aquamarine",
      +  "citrine",
      +  "quartz",
      +  "alexandrite"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description's job is to add content detail, which it does by naming the eight-score benchmark against the T73 round brilliant and the pros/cons payload. It stops short of describing pagination or error cases, but for a read-only lookup tool that is a minor gap.

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?

Two tight sentences, front-loaded with the payload description and closed with a usage cue. Nothing is redundant, though the middle clause listing the eight scores is slightly dense.

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?

There is no output schema, so the description usefully carries the burden of explaining what comes back (headline, eight comparative scores, pros/cons). With both parameters fully documented in the schema and the alias-stone caveat included there, the definition 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 coverage is 100%, with the gemstone enum and alias-stone behavior fully documented in the schema itself. The description adds no syntax or format detail for the 'cut' or 'gemstone' inputs beyond what the schema already provides, so the baseline of 3 applies.

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 states specifically what the tool returns for a single cut/gemstone pair: a headline, eight measured scores benchmarked against the T73 round brilliant, and pros and cons. That level of specificity clearly separates it from siblings like get_cut_scores or best_cuts_for_gemstone, which operate at different scopes.

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 ending clause gives a concrete question shape ('is an oval a good cut for sapphire?') that tells the agent exactly when this tool applies. It does not explicitly exclude sibling tools such as compare_cuts or best_cuts_for_gemstone, so the routing guidance is clear but not exhaustive.

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.