Skip to main content
Glama

Get a VYKA Score

vyka_score
Read-onlyIdempotent

Returns VYKA's 0–100 quality score for a diamond and how it was calculated. Use this when the user asks for the VYKA Score of a stone in VYKA's inventory (give its report number or VYK code) or wants a diamond they describe scored on VYKA's scale (give type, shape, carat, colour and clarity, and any of cut, polish, symmetry, fluorescence, lab, eye-clean and proportions). Limits: it is VYKA's own guide computed from the report figures, not a laboratory grade; natural and lab-grown diamonds are scored on separate scales that do not compare; only white diamonds in the ten main shapes are scored; figures left out make the score less certain (figures_used shows how many were used).

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

Input Schema

NameRequiredDescriptionDefault
cutNo
labNoThe grading laboratory, if known.
codeNoA report number or VYK code of a stone VYKA lists. Use either this or the specs below.
typeNo
caratNo
shapeNo
colourNo
polishNo
clarityNo
symmetryNo
width_mmNo
eye_cleanNoTrue when the listing says the stone is eye-clean, false when it says it is not. Leave out when unknown.
length_mmNo
crown_angleNo
fluorescenceNo
depth_percentNo
table_percentNo
pavilion_angleNo

Output Schema

NameRequiredDescriptionDefault
kindYes
noteYes
tierYesExceptional 90+, Excellent 80s, Very good 70s, Good 60s, Fair below 60.
partsYes
scaleYes
scoreYes0–100.
stoneYes
summaryYes
strengthsYes
tradeoffsYes
method_urlYesHow the score works, on vykadiamonds.com.
figures_usedYes
figures_totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe, read-only, idempotent, non-destructive, closed-world operation, yet the description adds substantial context beyond them: the score is computed from report figures rather than graded, natural and lab-grown scales are not comparable, coverage is limited to white diamonds in ten main shapes, and missing figures reduce score confidence. The note that figures_used reveals how many inputs were used is exactly the kind of output-behavior detail that helps an agent interpret results.

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?

Content is front-loaded with purpose first, then usage paths, then limits, and no sentence is filler. The long parenthetical listing optional fields is dense but functional; a slightly tighter break between the two invocation modes would aid scanning.

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?

An output schema exists, so return values need no explanation, and the description focuses on what the schema cannot convey: the two input modes, the scope limits, and how missing figures affect confidence. For an 18-parameter optional-only tool, this covers everything an agent needs to call it correctly and interpret the result.

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 only 17%, so the description must carry meaning, and it largely does: it enumerates the spec set (type, shape, carat, colour, clarity, cut, polish, symmetry, fluorescence, lab, eye-clean, proportions) and signals that only the first group is core while the rest are optional ('any of'). It also clarifies the code-versus-specs exclusivity. It stops short of explaining enum values or the individual proportion limits, which the schema still covers via ranges.

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 names a specific verb and resource — 'Returns VYKA's 0–100 quality score for a diamond and how it was calculated' — so the output is unambiguous. It is clearly distinct from siblings like get_diamond or check_report because it produces a proprietary computed score rather than raw listing data or a lab report lookup.

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?

It gives two explicit invocation paths with the inputs each requires: a stone in VYKA inventory (report number or VYK code) versus a user-described stone (type, shape, carat, colour, clarity, plus optional grading/proportion fields). It also states boundaries — not a lab grade, separate scales for natural vs lab-grown, only white diamonds in ten shapes — which tell the agent when the tool is unsuitable.

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