Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: add a sealed record

car_record_add

Append one entry to the vehicle's hash chain: an odometer reading, service, repair, inspection, trip (distance and time only), fuel, charge, accident, title change or note. Each entry is hashed with the one before it, so history cannot be edited quietly. An odometer reading lower than an earlier one is recorded and flagged as a rollback.

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>",
      "type": "<type>"
    },
    "name": "car_record_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoAny of: odometer, unit (km|mi), distance, duration_min, liters, kwh, cost_usd, summary, date (YYYY-MM-DD). No location.
typeYesodometer | service | repair | inspection | trip | fuel | charge | accident | title | note
vehicleYesvehicle_id (car_...) or the 17-character VIN
owner_keyYesThe owner_key (carkey_...) returned by car_register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent, closed-world write, and the description usefully adds behavior beyond that: entries are hash-chained to the previous one, history 'cannot be edited quietly', and out-of-order odometer readings are recorded but flagged as rollbacks. It does not state what the call returns or whether the owner_key grants write authorization, but the tamper-evidence and rollback semantics are exactly the kind of extra context that earns credit.

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?

Three sentences, front-loaded with the action, then the integrity guarantee, then the one notable edge case. No filler and no restatement of the tool name.

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?

There is no output schema, yet the description covers the write semantics, the tamper-evidence guarantee, and the notable rollback-flagging behavior, which is what an agent needs. It could be slightly stronger by saying what a successful append returns or that records cannot be deleted or amended, but nothing critical is missing for a four-parameter append tool.

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 input schema already documents vehicle, owner_key, type, and every data field including the 'No location' constraint. The description contributes one extra constraint, that trip records carry distance and time only, which is marginal beyond the schema, so the high-coverage baseline of 3 applies.

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 ('Append one entry to the vehicle's hash chain') and then enumerates the full scope of record types it accepts, so an agent can tell it apart from read-side siblings like car_history or car_verify without opening a schema. The purpose is unambiguous and fully bounded.

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?

The list of record types functions as clear when-to-use guidance, and the parenthetical '(distance and time only)' constrains how to use the trip type. It does not name alternatives or state prerequisites explicitly (e.g. that the vehicle must already be registered and that it only appends, never updates), so it stops short of full routing guidance.

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