Skip to main content
Glama

Digital Gemology: gemstone and diamond cut library

List the gemstones

list_gemstones
Read-onlyIdempotent

The 30 gemstones we score cuts in, with refractive index, critical angle, dispersion, hardness and specific gravity, and the three best cuts of each kind. An alias stone names the stone whose figures it shows (cut_scores_from).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: it fixes the result size (30 stones), lists the exact figures returned including the three best cuts per stone, and explains the alias-stone quirk via cut_scores_from, which is not derivable from any structured field.

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 sentences, front-loaded with the resource and the fields, with no filler. The second sentence on alias stones is terse and slightly cryptic out of context, but it conveys information that would otherwise be missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does carry the return-shape burden and does so reasonably by enumerating fields and result count. However, it does not indicate structure (per-stone object vs. flat records) or ordering, and the alias-stone behavior is left half-explained, so an agent still has gaps about the exact payload.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of cut_scores_from is a data field rather than an input, so it does not function as parameter guidance.

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 names a specific verb and resource ('the 30 gemstones we score cuts in') and enumerates the attributes returned (refractive index, critical angle, dispersion, hardness, specific gravity, three best cuts). It is unmistakably a catalog-listing tool, distinct from the cut-oriented siblings, though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer this is the discovery step before calling best_cuts_for_gemstone or get_cut_scores, but the description never states when to use this versus those alternatives or any prerequisite ordering.

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.