Skip to main content
Glama

SilkVin — wholesale parts for Chinese cars

Look up an OE number

lookup_oe
Read-onlyIdempotent

Find which SilkVin catalogue line or core-range reference carries an OE (or aftermarket) part number. Dashes, spaces and dots are ignored.

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": {
      "oe": "<oe>"
    },
    "name": "lookup_oe"
  }
}

Input Schema

NameRequiredDescriptionDefault
oeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely non-derivable behavioral trait — that dashes, spaces and dots in the input are ignored during matching — which is real value. It says nothing about match cardinality (single best match vs. multiple lines) or no-match behavior, which remain gaps.

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?

Two short sentences, both earning their place: the first states the purpose, the second states the input normalization rule. Purpose is front-loaded and there is no redundant restatement of the title or name.

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

Completeness3/5

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

There is no output schema, so the description is the only place an agent could learn what comes back — and it only hints at a catalogue line or core-range reference without saying whether results are a list, a single match, or how ambiguity is resolved. For a one-parameter read-only lookup that is borderline adequate, but the response shape and no-match case are left to discovery.

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?

The single parameter has zero schema description coverage, so the description must carry the meaning — and it does: the value may be an OE number or an aftermarket number, and punctuation is normalized away. That is meaningful guidance an agent could not get from {"oe": string}. It does not state format constraints (length, allowed characters beyond the punctuation rule), keeping it at 4.

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 uses a specific verb+resource pair: find which catalogue line or core-range reference carries an OE (or aftermarket) part number. That is a reverse lookup, which an agent can distinguish from a forward lookup like get_part. It stops short of naming or contrasting with the sibling tools (search_parts, get_part), so it lands at 4 rather than 5.

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?

Usage is implied: you have an OE or aftermarket number and want to know which catalogue line carries it. There is no explicit when-to-use/when-not, no mention of what to do when the number is not found, and no pointer to alternatives for name- or spec-based lookups. Adequate but inferential.

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