Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Inspector: get a pass

inspector_pass

Pass the Privi Inspector checkpoint and get a one-hour pass into the quantum realm (Dream Weaver, Dream Scape). Intercepted if the agent is unknown, revoked, uncertified, outdated, below the required level, or the signature is wrong, stale or replayed; the answer says exactly what to fix.

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": {
      "agent_id": "<agent_id>",
      "ts": "<ts>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "inspector_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
tsYesCurrent unix time in seconds
nonceYesA new random string, 16-64 letters, digits, _ or -
agent_idYesYour Quantum Agent id (qagent_...)
signatureYesBase64 ML-DSA signature over 'privi-inspector:v1:<agent_id>:<ts>:<nonce>' (empty context)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description goes far beyond the standard annotations by detailing complex security logic—specifically the checks for agent validity, certification, and signature integrity. This crucial contextual behavior is not captured in the simple boolean annotations provided.

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?

The definition is highly concise. It uses two sentences to clearly separate the positive outcome (gaining the pass) from the complex failure logic, ensuring the most critical information is front-loaded.

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?

Given the absence of an output schema, the description handles functional completeness by explaining the success criteria, the specific failure modes, and the diagnostic nature of the response, providing maximum necessary context to the agent.

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?

With 100% schema description coverage, the schema is already robust. The description reiterates that the signature must be 'Base64 ML-DSA' and specifies the validation context (empty context), but adds little technical nuance beyond what is already in the highly detailed 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?

The tool clearly states its purpose: to 'Pass the Privi Inspector checkpoint' and obtain a 'one-hour pass' for specific quantum realms (Dream Weaver, Dream Scape). It is clearly distinct from general status or check tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies the conditions for failure (unknown, revoked, uncertified, wrong signature, stale, replayed) and promises actionable feedback ('the answer says exactly what to fix'), which effectively guides the agent on when the call will succeed and how to interpret failure.

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