Skip to main content
Glama

SilkVin — wholesale parts for Chinese cars

Catalogue line detail

get_part
Read-onlyIdempotent

Full detail of one catalogue line by id (from search_parts): models, years, engine, OE numbers, aftermarket equivalents with sources, measurements, what to send to get it quoted, typical markets and page.

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": {
      "id": "<id>"
    },
    "name": "get_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description contributes the return payload ('models, years, engine, OE numbers, aftermarket equivalents with sources, measurements, what to send to get it quoted, typical markets and page'), which is useful since no output schema exists, but says nothing about behavior on an unknown id or id format expectations.

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?

One dense sentence with the resource and lookup key front-loaded, followed by a compact enumeration of returned fields. No filler, hedging, or repetition; every clause conveys information.

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 single-record read tool with one param and no output schema, the description covers both the input provenance and the shape of the return value, which is the main thing an agent needs. The remaining gap is failure behavior for an invalid or stale id, which is minor for a read-only operation whose annotations are already thorough.

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?

There is a single parameter with 0% schema description coverage, so the description must carry the burden. It does partially, clarifying that 'id' identifies a catalogue line and originates from search_parts, but it never states the expected format (string shape, prefix, case) an agent would need to construct a valid value.

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 gives a specific verb and resource ('Full detail of one catalogue line by id') and enumerates the fields returned, so an agent knows this is a single-record fetch rather than a list. It references search_parts as the id source, which implicitly distinguishes it from the search sibling, though the overlap with lookup_oe (both surface OE numbers) is left unresolved.

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 parenthetical '(from search_parts)' communicates the intended workflow: obtain an id from search_parts, then call this tool for detail. That is clear contextual guidance, but there are no explicit exclusions telling the agent when to prefer lookup_oe or request_quote instead.

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