Skip to main content
Glama

Diamonds Expert

Подготовить запрос на подбор

prepare_selection_request
Read-only

Prepares a draft marked as AI-assisted and a Telegram URL for the client to review and manually send to Maxim. Never submits, reserves, buys or contacts anyone. Missing budget/country details are returned as questions. Optional reference_id must come from estimate_retail_price and match the stone; it expires after 30 minutes. Use the calculated retail reference and report a discount only when it is known. Show the full draft to the client before opening Telegram.

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

Input Schema

NameRequiredDescriptionDefault
cutNo
labNo
caratYes
colorYes
shapeYes
budgetNo
originYesOnly natural diamonds.
polishNo
wishesNo
clarityYes
symmetryNo
budget_scopeNo
fluorescenceNo
reference_idNo
budget_currencyNo
destination_countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description goes well beyond them by confirming it never submits, reserves, buys or contacts anyone, that it emits a draft plus Telegram URL rather than performing the send, that reference_id expires after 30 minutes, and that gaps are surfaced as questions. These are the operational facts an agent needs and none of them are in the structured fields.

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 purpose, then constraints, then procedure — dense and mostly waste-free. A couple of imperative coaching sentences ("Show the full draft to the client before opening Telegram") sit alongside specification, mixing instructions with description, but they still carry real behavioral meaning.

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?

For a 16-parameter, no-output-schema tool the description covers the returned artifacts, the no-side-effect guarantee, the reference expiry, and the missing-data path, which is most of what an agent must know. The remaining gap is per-parameter meaning on a low-coverage schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 16 parameters and only 6% schema description coverage, the description must carry the burden, but it only explains reference_id in depth and gestures at budget/destination_country. Ambiguous fields such as budget_scope (total vs stone vs unspecified), wishes, lab, and the "Discuss" enum values for cut/polish/symmetry/fluorescence get no clarification at all.

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?

"Prepares a draft marked as AI-assisted and a Telegram URL" gives a concrete verb and two concrete artifacts, and the tool is clearly delineated from estimate_retail_price, which it only consumes by reference. An agent knows exactly what comes back without opening the schema.

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 specifies the upstream dependency (reference_id must come from estimate_retail_price and match the stone), the human-in-the-loop step sequence (show draft, then open Telegram), and that missing budget/country data comes back as questions rather than an error. It does not explicitly say when to prefer this over the sibling estimate/compare tools, but the workflow context is clear enough to route correctly.

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