Agent Services (x402): compliance, company, procurement

VIN Decoder + Safety Recalls (NHTSA) ($0.003)

vin_decode

Read-onlyIdempotent

[Data utilities] Identify a vehicle from its VIN and check for safety recalls before a purchase, listing, insurance quote or repair. Use when a VIN is all you have; coverage is best for US-market vehicles. Price: $0.003 per call (USDC on Base, x402). Returns the x402 payment requirements unless payment_signature is given. Sample: /samples/vin-decode

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": {
      "vin": "<vin>"
    },
    "name": "vin_decode"
  }
}

Input Schema

Name	Required	Description
`vin`	Yes	17-character Vehicle Identification Number
`recalls`	No	Include recalls (default true)
`payment_signature`	No	Optional x402 v2 PAYMENT-SIGNATURE value, relayed unchanged to the endpoint. Omit to receive the payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations cover safety (readOnly, idempotent, openWorld), and the description adds substantial context beyond them: the $0.003 price, the x402 payment model on Base, and critically that the call returns payment requirements unless a payment_signature is supplied. That auth/payment flow is exactly the kind of behavioral detail annotations cannot express.

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?

Purpose is front-loaded, followed by usage, then pricing/payment behavior and a sample reference. Dense but each sentence carries information; the pricing parenthetical and sample path are slightly list-like but not wasteful.

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 read-only lookup with no output schema, the definition covers the key operational facts: coverage limits, cost, and the payment handshake. It does not sketch the shape of the decoded result, which is a minor gap given no output schema exists to carry that.

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 description coverage is 100%, so the schema already documents vin, recalls, and payment_signature fully. The description only reinforces the payment_signature behavior ('Returns the x402 payment requirements unless payment_signature is given'), which is marginal added value over the structured field.

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: identify a vehicle from its VIN and check safety recalls. No sibling tool performs VIN decoding, so there is no ambiguity to disambiguate, and the enumerated use cases (purchase, listing, insurance quote, repair) sharpen the purpose further.

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 a clear selection condition ('Use when a VIN is all you have') and a coverage caveat ('best for US-market vehicles'). No alternatives exist among siblings, so the absence of explicit when-not-to-use routing is acceptable, but it stops short of the full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Services (x402): compliance, company, procurement tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?