Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: check a VIN

car_vin_check
Read-onlyIdempotent

Validate a VIN's format and its check digit (position 9, required in North America) and return the fingerprint Privi Car stores in place of the VIN. Catches typos and many made-up VINs. It does not look the vehicle up in any outside database.

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": "car_vin_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes17-character vehicle identification number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety bar is lower; the description still earns credit by disclosing the check-digit rule (position 9, North America) and that no external database is queried, which substantiates openWorldHint=false. It does not describe failure behavior (what a malformed VIN yields) or the fingerprint's format, keeping it below 5.

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 tight sentences, front-loaded with the action and result, then a scope-limiting clause. No filler and nothing repeated from the title or schema.

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

Completeness5/5

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

For a one-parameter read-only validator with no output schema, the description covers input expectations, output (a stored fingerprint), and the key limitation (no external lookup), which is everything an agent needs to call it correctly.

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?

With a single parameter and 100% schema coverage the baseline is 3; the description adds real meaning by explaining what the 'vin' string is validated against (format plus position-9 check digit, NA requirement). It does not specify accepted characters or edge cases such as lowercase input.

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 ('Validate a VIN's format and its check digit') and adds the non-obvious output ('the fingerprint Privi Car stores in place of the VIN'). The closing sentence explicitly bounds the scope by denying an outside database lookup, so an agent can distinguish this from lookup-style siblings without opening the schema.

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 clear usage context: use it to catch typos and many made-up VINs, and it is not a vehicle lookup against an outside database. This establishes when-not-to-use it for enrichment purposes. It stops short of naming a sibling alternative, so it is not a full 5.

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

All Privi Quantum toolsInspect
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