Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: issue a digital key

car_key_issue

Issue a time-limited, scope-limited key for a driver, valet, shop or buyer, signed Ed25519 + ML-DSA-87. Returns a token (shown once) for the grantee. A 'history' key opens car_history. unlock / drive / trunk / valet / service keys are credentials for hardware that checks them with car_key_check; Privi Car itself never opens or starts a vehicle.

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": {
      "vehicle": "<vehicle>",
      "owner_key": "<owner_key>",
      "grantee": "<grantee>",
      "scopes": "<scopes>"
    },
    "name": "car_key_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow long the key lasts, in hours (default 24, up to 366 days)
scopesYesOne or more of: history, unlock, drive, trunk, valet, service
granteeYesWho the key is for (stored only as a hash)
vehicleYesvehicle_id (car_...) or the 17-character VIN
owner_keyYesThe owner_key (carkey_...) returned by car_register
not_beforeNoOptional ISO 8601 start time; default now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the mutation/non-idempotent profile; the description adds the critical operational fact that the token is shown exactly once, plus the signing scheme and the time/scope bounding. It omits what happens to previously issued keys on re-issue and any owner_key authorization requirements.

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?

Front-loaded with the core action and constrained to four sentences where every one carries information. The slash-separated scope lists make it slightly denser to parse than necessary, but nothing is redundant.

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 6-parameter mutation tool with no output schema, the description covers the return value (single-use token), the safety boundary, and scope semantics. Gaps remain around key lifecycle (re-issuance, revocation interplay, owner_key authorization) that an agent would want before calling.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by attaching meaning to scope values that the schema merely enumerates: 'history' opens car_history, while unlock/drive/trunk/valet/service are hardware credentials verified via car_key_check. hours and not_before are left to the schema.

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 precise verb+resource: issue a time-limited, scope-limited key for a named class of grantee, cryptographically signed. It also draws a clear boundary against siblings by explaining that 'history' keys feed car_history and hardware credential scopes are consumed by car_key_check, not by Privi Car itself.

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 real context for choosing scopes and clarifies what the tool does NOT do (never opens or starts a vehicle), which routes the agent correctly toward car_key_check for actual use. It stops short of stating explicit when-not conditions, such as rotation or re-issue versus car_key_revoke.

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