Skip to main content
Glama

Request a parts quote from Dabit

request_quote
Destructive

Submits a non-binding quote request for physical electronic components to Dabit, the company that operates PartsPlan. Use when the user asks Dabit to quote parts. The request (part numbers, quantities, destination country and the conditions the user stated) is stored and emailed to Dabit, who replies by email to the verified email of the user's PartsPlan account (or to another address the user gives, with the account email copied), also when it cannot supply the parts. International orders are paid in advance. Submit after the user confirms the items, destination and use of their verified PartsPlan account email; do not repeat an already given confirmation. Ask only for a missing destination country or to clarify an unclear part number or quantity; optional fields carry only what the user already said and are not a questionnaire. No order, payment or stock reservation is made. An identical request from the same account within 24 hours returns the original reference. Limits: 50 lines per request, 5 requests per account per 24 hours, and a service-wide daily limit.

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

Input Schema

NameRequiredDescriptionDefault
itemsYesParts to quote, one line per part number (1 to 50).
reply_emailNoEmail address for the reply, only when the user asks to receive it at an address other than their PartsPlan account email. The account email still gets a copy.
organizationNoCompany or institution to address the quote to, only when the user names it for this quote.
requirementsNoPurchasing conditions the user stated (for example "full reel", "date code 2024 or newer", "manufacturer CoC"), up to 10, 1000 characters in all. No conversation summaries, project details, customer names or personal data.
reply_languageNoLanguage of the email reply: ko (Korean) or en (English, the default).
ship_to_countryYesCountry the parts would ship to, as a two-letter ISO 3166-1 code (US, DE, KR …), stated or confirmed by the user. Do not infer it from language, IP address or email domain.

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes
quote_refNo
retryableNo
doc_sha256No
item_countNo
reply_fromNo
request_idNo
limit_scopeNo
retry_after_msNo
withdrawn_noteNo
retry_after_secondsNo
withdrawn_documents_omittedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag it as non-read-only, open-world, non-idempotent and destructive; the description goes far beyond that by explaining that the payload is stored and emailed to a third party, that the reply goes to the verified account email (or an alternate address with the account email copied), that international orders are paid in advance, and that no order/payment/reservation occurs. It also discloses the 24-hour duplicate-request dedup returning the original reference and hard limits (50 lines, 5 requests per account per 24h, service-wide daily cap) — the operational details an agent actually needs.

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 purpose and the non-binding guarantee, then behavior, then the confirmation rule, then limits — a sensible order with no filler. It is dense and long for a single paragraph, and the rate-limit sentence could arguably be tightened, but nearly every sentence carries decision-relevant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, third-party-facing mutation with nested arrays, the description covers trigger, confirmation timing, email routing, lack of order/payment side effects, dedup behavior, and three distinct limits. Because an output schema exists, return-value detail is unnecessary, and the description still mentions the returned reference in the dedup case.

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

Parameters4/5

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

Schema coverage is 100%, so per-field meaning is already supplied; the description's added value is a population rule — optional fields carry only what the user already said, and only a missing destination country may be asked for. That is genuine guidance beyond the schema, though it does not explain the items/requirements nested structure or the reply_email copy semantics in the prose itself (those live in the schema).

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?

"Submits a non-binding quote request for physical electronic components to Dabit" names a specific verb (submits), a specific artifact (non-binding quote request), and the counterparty, and the qualifier "non-binding" plus "No order, payment or stock reservation is made" cleanly separates it from transactional or inventory siblings such as check_stock or search_parts.

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?

States the trigger ("Use when the user asks Dabit to quote parts") and the precondition ("Submit after the user confirms the items, destination and use of their verified PartsPlan account email"), plus explicit exclusions: "do not repeat an already given confirmation". It even constrains follow-up questioning ("Ask only for a missing destination country or to clarify an unclear part number or quantity") and warns that optional fields are "not a questionnaire".

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.