Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: parked-car edge job gate (simulation)

car_edge_job

Research simulation of the admission gate for compute on a parked car's companion device. A job is admitted only with owner opt-in, vehicle parked, external power and safe temperature, a matching tenant, a fresh nonce and a short expiry; replays are rejected. Returns a digest receipt with zero credits. No job runs on any vehicle and no rewards are paid.

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": {
      "job": "<job>",
      "policy": "<policy>"
    },
    "name": "car_edge_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYes{tenant, nonce (32 hex), expiresAt (ms, within 60 s), payload (text up to 64 KB)}
policyYes{tenant, ownerOptIn, parked, externalPower, thermalSafe}; all four flags must be true

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 declare the tool is not read-only, not idempotent, not destructive and closed-world; the description adds real behavioral context beyond that: replays are rejected, nonces must be fresh, expiry is short, and it returns a digest receipt with zero credits while no job runs and no rewards are paid. It does not discuss what state the receipt write actually persists, but given annotations already cover the mutation profile this is solid.

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 dense sentences, front-loaded with the simulation framing and safety disclaimer before admission criteria. Nothing is redundant or padded.

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 carries the return-behavior burden and does say a digest receipt with zero credits comes back. Combined with the admission rules and the 'nothing runs on any vehicle' disclaimer, an agent has enough to call it correctly; only the failure/response shape for rejected jobs is left implicit.

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 coverage is 100% and the nested schema already documents tenant, nonce (32 hex), expiresAt (within 60 s), payload size, and that all four policy flags must be true. The description restates those constraints rather than extending them (e.g., no guidance on what happens to payload contents or how a tenant mismatch is reported), so the baseline 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 names a specific verb/resource pairing – an admission gate for a compute job on a parked car's companion device – and immediately qualifies it as a 'research simulation.' That framing plus the sibling set (car_charge_plan, car_key_issue, etc.) makes it unambiguous what this does and does not do.

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?

The description lists the admission conditions (owner opt-in, parked, external power, safe temperature, tenant, nonce, expiry) but never says when an agent should choose this over another job-submission tool, nor does it name any alternative or exclusion. Usage is implied by the 'research simulation' framing rather than stated.

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