Skip to main content
Glama

Digital Gemology: gemstone and diamond cut library

Search the cut library

search_cuts
Read-onlyIdempotent

Search Digital Gemology's gem cuts and Platonic solids by name, style, shape or use (for example 'square step cut', 'round brilliant for moissanite', 'historic cushion', 'pear'). Returns each match with its page, facets, size and price; get_cut gives the checkout links. Give a gemstone to add the cut's brilliance, fire and scintillation in that stone and to sort by them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_cuts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance (default with a query), total (brilliance + fire + scintillation, the default with a gemstone and no query), brilliance, fire, scintillation, facets (most first) or name.
limitNoHow many cuts to return, 1 to 50; 5 if left out.
queryNoFree text. Leave it out to list every cut that fits the filters.
shapeNoOutline of the cut.
categoryNobrilliants, jewelry (fancy and step cuts), historic, house (our own designs) or platonic (solids, 3D files only).
gemstoneNoGemstone, 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.
cutting_filesNoOnly cuts that are also sold as GemCad cutting files.

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. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -10New value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"How many cuts to return, 1 to 50; 10 if left out."New value: +"How many cuts to return, 1 to 50; 5 if left out."
  3. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many cuts to return, 1 to 50; 10 if left out."
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful context about what each match includes (page, facets, size, price), but says nothing about pagination behavior, total result counts, or what an empty result looks like. It complements the annotations without being unusually rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core search action and filtering axes, then the return payload, then the gemstone enrichment mode. Every clause carries information; nothing is repeated from the schema or the title. The example queries make the query parameter concrete without a parameter-by-parameter enumeration.

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?

For a 7-parameter, all-optional search tool with no output schema, the description compensates by summarizing the return shape (page, facets, size, price) and pointing to get_cut for checkout. The gemstone enrichment and sorting behavior is also explained, leaving nothing an agent would need in order to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents sort, limit, shape, category, gemstone and cutting_files thoroughly. The description adds meaning beyond the schema by explaining that a gemstone also enriches the results with brilliance/fire/scintillation values and enables sorting on them, connecting parameters to intent rather than restating enum values.

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 (search) and resource (gem cuts and Platonic solids), and enumerates the axes it searches on (name, style, shape, use) with concrete examples like 'square step cut' and 'round brilliant for moissanite'. It also names get_cut as the follow-up for checkout links, so an agent can separate lookup from purchase without opening either schema.

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?

Clear context for the two modes: plain text search to find cuts, and supplying a gemstone to add brilliance/fire/scintillation figures and sort by them, plus an explicit pointer to get_cut for checkout links. There are no exclusions or explicit comparisons against siblings like best_cuts_for_gemstone or compare_cuts, which leaves a small gap.

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.