Skip to main content
Glama

Qadiva — wholesale glassware (UAE & GCC)

Send a quote request

request_quote

Send a quote request to Qadiva for a business buyer (hotel, restaurant, caterer, distributor or retailer): references or descriptions with quantities, optional samples and logo decoration. It reaches the same inbox as the website form; Qadiva replies by e-mail with a written quote per piece in AED or USD. Only call this when the buyer asked for a quote and agreed to share their contact details.

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": {
      "buyer": "<buyer>",
      "items": "<items>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
buyerYes
itemsYes
messageNo
samplesNo
logo_decorationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds genuinely new information beyond that: the request lands in the same inbox as the website form, an external party replies by e-mail, the resulting quote is priced per piece in AED or USD, and buyer consent is a precondition. This explains the real-world side effect and its acknowledgement path, which the annotations cannot convey.

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 action and audience before the mechanics and then the gating condition. Every clause carries new information, with no restatement of the tool name or filler.

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, the description usefully explains what comes back (an e-mailed written quote per piece in AED or USD) and where the request is delivered. The remaining gap is the unmentioned agent and message parameters and nested buyer fields such as country scope, which an agent must infer from the schema alone.

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 0% across six parameters with nested objects, so the description has to compensate. It adds meaning for items (references or descriptions with quantities), samples and logo_decoration as optional extras, and mirrors the buyer business-type enum, but says nothing about the nested agent object, the message field, or the UAE/GCC country constraint.

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 ("Send a quote request to Qadiva") plus the target audience (business buyers: hotel, restaurant, caterer, distributor, retailer). This is clearly a write/outbound action, which separates it from the read-only catalog siblings get_piece, get_terms and list_glassware without needing their schemas.

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?

Gives an explicit negative gate: "Only call this when the buyer asked for a quote and agreed to share their contact details," which rules out speculative or browsing use. It does not name a sibling alternative explicitly (e.g., 'use get_piece/list_glassware to browse the catalog first'), so the routing half of the guidance is inferred from context rather than stated.

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