Skip to main content
Glama

Digital Gemology: gemstone and diamond cut library

Best cuts for a gemstone

best_cuts_for_gemstone
Read-onlyIdempotent

The top ten brilliants and the top ten jewelry cuts in one gemstone, ranked by brilliance, fire and scintillation added together, with the stone's optical constants.

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

Input Schema

NameRequiredDescriptionDefault
kindNobrilliants (round cuts), jewelry (fancy and step shapes) or both.both
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds return-shape information (two ranked top-ten lists plus optical constants and the combined ranking metric). It does not explain the ranking scale or the alias-stone substitution behavior, which is instead left to the schema.

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?

A single sentence with no filler: the ranking metric, the two result lists and the accompanying optical constants are all front-loaded. Every clause earns its place.

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 carries the return-value burden and does so adequately by naming both lists, the ranking criteria and the optical constants. It stops short of describing the numeric scale or the ordering presentation, a minor gap for a read-only lookup.

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 both enums are documented, including the alias-stone caveat, so the baseline is 3. The description reinforces that one gemstone is queried and hints at the brilliants-vs-jewelry split via the default 'both' case, but adds no meaning beyond the schema's enum text.

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?

States a concrete resource and result: the top ten brilliants and top ten jewelry cuts for a gemstone, ranked by brilliance, fire and scintillation summed, plus the stone's optical constants. That is far more specific than the title. It never distinguishes itself from siblings such as cut_in_gemstone or get_cut_scores, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description describes the output but gives no explicit when-to-use, when-not-to-use, or alternative. Nothing tells an agent whether to reach for this instead of cut_in_gemstone, get_cut_scores or recommend_cut. Usage is only implied by the purpose statement.

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.