Skip to main content
Glama

SilkVin — wholesale parts for Chinese cars

Search wholesale parts for Chinese cars

search_parts
Read-onlyIdempotent

Search SilkVin's wholesale catalogue of parts for Chinese vehicle brands (Chery, Omoda, Jaecoo, Jetour, Exeed, Haval/GWM, MG, Changan, BYD) by OE number, model, brand or part name. Returns catalogue lines (models, years, OE numbers, page) and core-range references. No prices are published. Wholesale only.

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": {
      "query": "<query>"
    },
    "name": "search_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYese.g. "Jolion brake pads", "Tiggo 7 Pro", "oil filter", "480-1012010"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the response contains catalogue lines (models, years, OE numbers, page) plus core-range references, and that prices are deliberately absent and the audience is wholesale-only.

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 short sentences, front-loaded with the capability, then the return contents, then the two commercial constraints. Nothing is redundant or padded.

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, describing the returned catalogue lines and the absence of pricing is exactly the right compensation, and the wholesale-only caveat prevents misuse. The only gap is pagination behaviour and the meaning of limit, which a 2-parameter search tool could reasonably spell out.

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 50%: the query parameter has an example-based description while limit has none beyond default 10 and max 50. The description compensates somewhat by naming the four fields query matches against (OE number, model, brand, part name), but says nothing about how limit affects results.

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?

States a specific verb and resource — searching SilkVin's wholesale parts catalogue — and enumerates the covered brands and the searchable fields (OE number, model, brand, part name). It does not explicitly distinguish itself from the sibling lookup_oe or get_part, so the boundary with an OE lookup tool is left for the agent to infer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Wholesale only" and "No prices are published" are real usage constraints that rule out retail/price-seeking queries, but the description never says when to prefer this over lookup_oe or get_part. Usage is implied by the searchable fields rather than stated as routing guidance.

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