Skip to main content
Glama

SilkVin — wholesale parts for Chinese cars

Trade terms

get_terms
Read-onlyIdempotent

Who SilkVin sells to, quality levels, warranty, payment, availability, what is not supplied, compliance and contacts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, non-destructive read operation. The description adds the useful scope detail that exclusions and compliance information are included, but it does not describe output format, auth requirements, or whether the terms are static or versioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and every listed topic is relevant, but it is a comma-separated fragment rather than a front-loaded statement of what the tool returns. A brief framing clause would improve structure without adding much length.

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 zero-parameter, read-only reference tool whose safety profile is already covered by annotations, the description is largely complete: it lists the substantive domains the terms cover. It could say more about the return format, but that gap is minor for this simple tool.

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 tool has zero parameters, so the baseline is 4. There are no parameter meanings the description needs to clarify.

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 enumerates exactly what trade terms are covered: selling regions, quality levels, warranty, payment, availability, exclusions, compliance, and contacts. That makes the resource clear despite lacking an explicit verb. It does not differentiate itself from siblings such as request_quote, so it falls short of a 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?

The content list implies this tool should be used for questions about SilkVin's commercial terms, but there is no explicit when-to-use or when-not-to-use guidance. No alternatives such as request_quote are mentioned.

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