Skip to main content
Glama

Contact a VYKA jeweller on WhatsApp

talk_to_jeweller
Read-onlyIdempotent

Returns a WhatsApp link to VYKA's sales line (+971 52 273 1161) with a pre-written first message, about a stone (report number or VYK code) or a vykadiamonds.com product page, in English or Arabic. Use this only when the user asks to contact VYKA, speak to a jeweller or enquire on WhatsApp. Limits: nothing is sent; the user opens the link, can edit the message and sends it themselves. No personal details are asked for or kept.

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

Input Schema

NameRequiredDescriptionDefault
stoneNoOptional: the stone's report number or VYK code.
languageNoLanguage of the message and the website link.en
product_urlNoOptional: a product page on vykadiamonds.com.

Output Schema

NameRequiredDescriptionDefault
phoneYes
messageYesThe pre-written text the user can edit before sending.
languageYes
stone_foundYesFor a stone: whether it is still listed. Null when no stone was given.
website_linkYesThe stone or product page the message refers to.
whatsapp_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds the genuinely surprising behavioral fact: nothing is sent, the user opens the link, edits the message and sends it themselves. It also discloses the privacy stance ('No personal details are asked for or kept'), which no annotation conveys. This is exactly the kind of context annotations cannot provide.

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 sentences, front-loaded with the core behavior, then the usage trigger, then the limits and privacy note. No redundancy, and the phone number and supported languages are placed where they are immediately useful.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile; the description fills the behavioral and privacy gaps. The only loose end is the all-optional parameter set — it never states the behavior when zero arguments are supplied or whether the two targeting parameters are mutually exclusive.

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 100%, so the baseline is 3. The description restates that the stone can be a report number or VYK code, that product_url is a vykadiamonds.com page, and that language governs both the message and the website link — useful but largely duplicative of the schema. It does not say whether stone and product_url can be combined or what happens when all optional parameters are omitted.

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 concrete verb and resource: it returns a WhatsApp link to VYKA's sales line with a pre-written first message, scoped to a stone (report number or VYK code) or a product page, in English or Arabic. That is precise enough to separate it from every sibling (vyka_score, check_report, get_diamond, search_diamonds), none of which are contact tools.

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 states an explicit trigger set ('when the user asks to contact VYKA, speak to a jeweller or enquire on WhatsApp') and an explicit restriction ('Use this only when...'). The when-not condition is directly encoded, so an agent can route to it or away from it without inference.

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