Skip to main content
Glama

SilkVin — wholesale parts for Chinese cars

Request a wholesale quote

request_quote

Send a request for quotation to SilkVin on behalf of a trade buyer (importer, distributor, wholesaler, parts store or workshop network). Lines can be OE numbers, catalogue line ids or free-text parts, with estimated quantities. Creates a case reviewed by a person; the written quote (price, Incoterm, lead time) follows by e-mail, normally within 48 working hours. Nothing is binding. Only call this when the buyer asked for a quote and agreed to share their contact details with SilkVin.

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>",
      "lines": "<lines>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
buyerYes
linesYes
notesNo
incotermNo
destination_portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag openWorldHint and non-readOnly, but the description goes well beyond them: it discloses that a human-reviewed case is created, that the quote arrives by e-mail normally within 48 working hours, that nothing is binding, and that contact details leave the buyer's environment. Those are exactly the side effects an agent needs before committing a user's data to a third party.

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-loads the verb and recipient, then layers constraints and the human-review outcome without filler; roughly five sentences, all of which carry information. The parenthetical buyer list mildly duplicates the business_type enum and could be trimmed.

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 nested-payload submission tool with no output schema, the description covers what happens after the call (case created, e-mailed quote, timeframe, non-binding) and who must consent. It does not say what the immediate response returns (e.g. a case reference) or what happens on rejection, which are the remaining gaps.

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?

With schema coverage reported at 0%, the description does real work by explaining that each line may be an OE number, a catalogue line id, or free-text parts with estimated quantities, which clarifies the otherwise ambiguous one-of shape of the line objects. It says nothing about incoterm, destination_port, notes, or the agent object, leaving four of six parameters without added meaning.

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 request for quotation to SilkVin") plus the actor it acts for (a trade buyer), and the sibling set (get_part, lookup_oe, search_parts) is clearly read-only lookup territory that this write-style request is not. An agent can distinguish it 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?

Gives an explicit gating condition: "Only call this when the buyer asked for a quote and agreed to share their contact details with SilkVin," which effectively states when not to call it. It does not name an alternative tool for agents who merely want pricing context, so it falls short of full when/when-not/alternatives coverage.

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