Skip to main content
Glama

Diamonds Expert

Рассчитать рекомендованную цену в ритейле

estimate_retail_price
Read-only

Returns a recommended retail price reference in USD for a natural diamond. In Russian, present it as «Рекомендованная цена в ритейле», calculated «по стандартам отрасли». Round uses the existing Round data; other supported shapes use the Pear data as instructed by the expert. Preserve table_shape, table_basis, shape_proxy, weight approximation notes and the data date. No shape-specific discount is invented. This is not an offer, inventory, transaction price or guaranteed discount. Market discounts depend on market conditions; Maxim sources the best proposal, checks the stone against its certificate and arranges destination delivery. Do not infer affordability in a different currency.

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": {
      "origin": "<origin>",
      "shape": "<shape>",
      "carat": "<carat>",
      "color": "<color>",
      "clarity": "<clarity>"
    },
    "name": "estimate_retail_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
caratYes
colorYes
shapeYes
originYesOnly natural diamonds.
clarityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly, openWorld, non-destructive), the description discloses genuinely non-obvious behavior: Round uses existing Round data, other shapes fall back to Pear data as a proxy, table_shape/table_basis/shape_proxy and weight-approximation notes must be preserved, and no shape-specific discount is invented. It also warns that discounts depend on market conditions and that affordability must not be inferred in another currency. What it does not cover is whether the returned figure is per-carat or total, and how volatile the underlying data is despite idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, but the text then mixes presentation rules ('In Russian, present it as…'), output-preservation instructions, legal caveats, and marketing copy about Maxim sourcing proposals and arranging delivery. The delivery/sales sentence does little to help an agent call the tool correctly and dilutes the operational content.

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?

With no output schema and only five required params, the description does a solid job naming the output fields to preserve (table_shape, table_basis, shape_proxy, weight approximation notes, data date) and warning against invented discounts or currency inference. Remaining gaps are the price basis (per-carat vs total) and any indication of uncertainty in the estimate.

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 only 20% (just the origin field), so the description must compensate; it adds real meaning for shape (proxy behavior across shapes) and carat (weight approximation notes), plus the USD currency context. It says nothing about color, clarity, or how the four Cs jointly drive the reference, leaving half the parameters under-explained.

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 states a concrete verb+resource: it returns a recommended retail price reference in USD for a natural diamond, and it pins the scope to natural stones and the four Cs implied by the schema. It does not name or differentiate itself from any sibling, though none of the listed siblings (knowledge_*, get_expert_profile, prepare_selection_request) appears to overlap.

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: the reader infers this is the tool for retail price estimation of a natural diamond, and the 'not an offer, inventory, transaction price' line bounds interpretation of the output rather than tool selection. There is no explicit when-to-use/when-not guidance and no routing to an alternative tool.

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