Skip to main content
Glama

Request a quote

request_quote
Idempotent

Send a price/quote request to Barmaan's sales team (same inbox as the website form). Ask the user for name and phone first; never invent contact details. Call once with confirm=false to get a preview, show it to the user, then call with confirm=true only after they agree.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "message": "<message>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer full name, asked from the user (never guessed).
emailNoCustomer contact email (optional). Stored for the sales team only; no confirmation email is sent to it.
phoneYesCustomer phone/WhatsApp with country code, asked from the user.
localeNoContent language: en, fa, ar or ckb.en
companyNo
confirmNofalse = preview only, nothing is sent. Set true ONLY after the user has explicitly agreed to send these exact details to Barmaan.
messageYesWhat the customer needs: product, quantity, specs, destination.
product_codeNo6-digit product code or product slug, if the request is about one product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Customer email (optional)."New value: +"Customer contact email (optional). Stored for the sales team only; no confirmation email is sent to it."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond annotations, the description discloses that requests go to the same inbox as the website form and that confirm=false returns a preview without sending anything. It also enforces user consent and prohibits inventing contact details, covering important behavioral constraints for an outbound sales request tool.

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?

The description is three concise sentences, front-loaded with purpose and then actionable workflow. Every sentence carries useful information with no redundant wording.

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 non-destructive, non-open-world submission tool with no output schema, the description covers the essential purpose, consent requirements, and preview/send sequence. It leaves some minor gaps around what the preview contains and what a successful submission returns.

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 coverage is high at 88%, so the schema already explains most parameters including confirm, name, phone, and message. The description reinforces the confirm preview/send workflow and contact-detail handling but does not add much beyond the schema for the remaining parameters.

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 clearly states a specific verb and resource: sending a price/quote request to Barmaan's sales team. The parenthetical about the website form adds useful context. It does not explicitly differentiate itself from sibling request tools such as request_create, so it stops short of the top score.

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?

The description gives clear usage context for requesting a quote and prescribes a concrete two-step workflow using confirm=false and confirm=true. It does not explicitly state when to use this tool instead of sibling request or catalog tools.

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