Skip to main content
Glama

Digital Gemology: gemstone and diamond cut library

Compare two cuts

compare_cuts
Read-onlyIdempotent

Two cuts side by side in one gemstone: overall, brilliance, fire, scintillation, tilt, face-up spread and leakage from the Cut Performance Index, each cut's place in that stone, facets and size, and the products with prices and checkout links. For questions like 'oval or pear for my 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_a": "<cut_a>",
      "cut_b": "<cut_b>"
    },
    "name": "compare_cuts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cut_aYesThe first cut's slug or name, for example 'oval'.
cut_bYesThe second cut's slug or name, for example 'pear'.
gemstoneNoThe stone to compare them in; diamond if left out.

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",
      +  "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. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered without description help. What the description adds is the returned content surface — the Cut Performance Index metrics, each cut's rank within the stone, facets/size, and purchasable products — which is real value because no output schema exists. It stops short of disclosing edge behavior, such as what happens when a cut is unavailable in the chosen gemstone.

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 scope statement is front-loaded and the example query at the end is a compact usage cue with no meta-commentary. The middle is a dense 'and…and…and' enumeration of metrics that reads like an output catalog; it is informative rather than padding, but it costs readability.

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 no output schema, the description carries the full burden of telling the agent what comes back, and it does so thoroughly — scores, per-stone ranking, physical attributes, and product links. All three parameters are documented elsewhere. What is missing is failure behavior (unknown cut, cut not offered in a gemstone) and any note on result size.

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%: both cut parameters are described with examples ('oval', 'pear') and gemstone carries a full enum plus an explicit 'diamond if left out' default. The description only reinforces the shared-gemstone framing ('in one gemstone') and adds no format or matching rules (e.g. how a slug vs. a display name is resolved). Baseline 3 is appropriate when the schema does the work.

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 opening clause 'Two cuts side by side in one gemstone' states a specific verb-like action and both resources, so an agent immediately knows this is a one-shot comparison of exactly two cuts. The rest of the sentence enumerates the comparison payload (overall, brilliance, fire, scintillation, tilt, spread, leakage, facets, size, products/prices). It never names a sibling such as best_cuts_for_gemstone or cut_in_gemstone, so differentiation is implied by 'side by side' rather than stated.

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?

'For questions like "oval or pear for my sapphire?"' gives a concrete trigger scenario that maps directly onto the two required parameters plus the optional gemstone. That is clear context for when to reach for this tool. There are no exclusions or explicit alternatives ('use X when you need only one cut's scores'), which keeps it short of a 5.

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.