Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: check a digital key

car_key_check
Read-onlyIdempotent

Is this key valid right now for this scope? Returns allowed true/false with the reason (expired, revoked, not yet valid, wrong scope), the vehicle_id and the signed attestation to verify offline.

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": {
      "token": "<token>"
    },
    "name": "car_key_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoOptional scope the holder wants to use
tokenYesThe key token (pck_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still earns credit by disclosing the failure-reason taxonomy (expired, revoked, not yet valid, wrong scope) and that a signed attestation is returned for offline verification — behavior an agent could not guess from the schema.

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 sentences, zero waste: the question form front-loads the purpose, and the return value is enumerated in the second sentence. No filler or repetition of annotation data.

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?

With no output schema, the description correctly takes on the burden of describing the return shape (boolean plus reason plus attestation), which is the key gap it needed to close. It does not address error behavior for malformed or missing tokens, a minor remaining gap for a two-parameter check.

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 both parameters are already documented, and the description only restates 'scope' implicitly via the 'wrong scope' reason. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no syntax or format guidance for the token.

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?

The description opens with a specific verb and resource ('Is this key valid right now for this scope?') and immediately states the return payload (allowed true/false, reason, vehicle_id, attestation). That distinguishes it cleanly from the issue/revoke siblings without naming them.

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 by the validation framing — an agent can infer it is the pre-flight check before acting on a key — but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., car_key_issue for new keys). The 'right now' phrasing hints at a time-of-check call but never states the prerequisite flow.

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