Skip to main content
Glama

Get one VYKA diamond

get_diamond
Read-onlyIdempotent

Returns one diamond from VYKA's diamond inventory by its certificate (report) number or VYKA stone code (VYK-…), with the details its page on vykadiamonds.com shows: grades, measurements, AED price (plus an indicative currency), photo, its page link and the laboratory's report-check link. Use this when the user gives a report number or VYK code, or to re-check a stone from search_diamonds before they decide or contact VYKA. Limits: only stones VYKA currently lists can be found. found is false when VYKA does not list that number now (it may have sold, or VYKA may never have listed it); that says nothing about whether the report is genuine, and report_check_links then gives the laboratory's own check. It does not verify the report itself.

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": {
      "code": "<code>"
    },
    "name": "get_diamond"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesA GIA or IGI report number (e.g. 2141438171) or a VYKA stone code (e.g. VYK-I-612345678).
currencyNoCurrency for the indicative price beside the AED price.AED

Output Schema

NameRequiredDescriptionDefault
codeYesThe report number that was looked up.
foundYes
diamondsYesUsually one; more when two laboratories used the same number.
report_check_linksNoOnly when found is false: the laboratory report-check pages this number's format fits. The links are only built, not opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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, and the description adds real value on top: only currently listed stones are findable, found=false is an expected outcome rather than an error, and that outcome says nothing about report authenticity. It stops short of covering rate limits or pagination, but for a single-record lookup the behavioral picture is close to complete.

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?

Front-loaded with the core action and accepted identifiers, then usage, then limits — a sensible ordering with no filler sentences. It is a single dense paragraph, so the limits and non-verification caveats are slightly harder to scan than they could be.

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?

Despite an output schema existing, the description still summarizes what comes back, and it covers the edge case an agent most needs to handle (found=false meaning sold or never listed). For a two-parameter lookup tool with full schema coverage and annotations, nothing material is missing.

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 coverage is 100%, so baseline is 3, but the description adds meaning by clarifying that the code is either a GIA/IGI report number or a VYKA stone code and by framing the currency parameter as producing an 'indicative currency' alongside the AED price. That clarifies intent (display currency, not pricing logic) beyond the enum list.

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 and resource ('Returns one diamond from VYKA's diamond inventory') and names both accepted identifiers (certificate/report number or VYK- stone code). It also enumerates the returned fields (grades, measurements, AED price, photo, page link, report-check link), so an agent can distinguish it from search_diamonds and check_report without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit triggering conditions ('when the user gives a report number or VYK code') and a secondary use case ('re-check a stone from search_diamonds before they decide or contact VYKA'). It also draws the boundary against verification by stating 'It does not verify the report itself', implicitly routing that need to check_report.

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.

Resources