Skip to main content
Glama

diamond-mcp

by io.github.JacobiusMakes

Define a diamond or gemology term

define
Read-onlyIdempotent

Look up a single diamond or gemology term in the encyclopedia of 90 adversarially fact-checked entries. Matches the term exactly (case insensitive), then by substring or related-term alias. Returns the full entry: definition, body, sourced claims, and related terms. If nothing matches, returns the three nearest term suggestions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesThe term to define, for example "Dutch Marquise" or "bow-tie effect". Case insensitive.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark it read-only and idempotent; the description adds the matching order, the full entry contents, and the no-match fallback to nearest suggestions. This is meaningful behavioral context beyond the annotations and reveals no contradiction.

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 tight sentences with no filler, and the most important behavioral details are front-loaded. Every sentence contributes either to purpose, matching semantics, or return shape.

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 single-parameter read-only lookup, the description fully covers invocation and expected return behavior, including the no-match case. The absence of an output schema is compensated by the explicit list of returned fields.

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?

With 100% schema coverage and a single documented `term` parameter, the baseline is 3. The description adds value by explaining the lookup algorithm (exact, then substring/alias) and the fallback behavior, which helps the agent predict what `term` will do.

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 opens with a specific verb-resource pair: 'Look up a single diamond or gemology term in the encyclopedia...' and details what is returned. This clearly distinguishes `define` from broad siblings like `search_encyclopedia` by emphasizing single-term lookup.

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?

It establishes when to use the tool: for a single exact term, with a deterministic matching fallback to substring or alias. It does not explicitly name alternatives such as `search_encyclopedia` or say when not to use it, so it falls 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.

All diamond-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target clearly distinct actions: searching, fetching details, looking up terms, verifying reports. The main ambiguity is between define and dutch_marquise_definition, since the latter appears to be a single encyclopedia entry surfaced as a standalone tool.

Naming Consistency3/5

All names are snake_case and readable, but the set mixes verb-led names like search_inventory and get_product with noun-phrase names like lab_grown_price_index and dutch_marquise_definition. The pattern is not consistent enough to predict the tool name from the action alone.

Tool Count5/5

Ten tools is well within the ideal range for a server that handles both diamond education and catalog shopping. Each tool contributes to a clear workflow: learn about diamonds, search inventory, fetch product details, and verify grading reports.

Completeness4/5

The tool surface covers the main user journey: research terms, search inventory, get product detail, understand grading, and verify reports. Minor gaps exist, such as only having a dedicated definition for the Dutch Marquise cut while other shapes rely on the general encyclopedia lookup.

Resources