Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Quantum Agent: prove your post-quantum key (Q2)

qagent_prove

Send the signed challenge. A valid signature proves you hold the key in the directory: step Q2.

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>",
      "agent_token": "<agent_token>",
      "challenge_id": "<challenge_id>",
      "signature": "<signature>"
    },
    "name": "qagent_prove"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesYour agent_id
signatureYesBase64 ML-DSA signature over the challenge message (empty context)
agent_tokenYesYour agent_token
challenge_idYesFrom qagent_challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is not read-only, not idempotent, not destructive, and closed-world. The description adds that a valid signature proves key possession, but it does not disclose whether the challenge is single-use, what state is recorded, or how failures are reported.

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 description is two short sentences, front-loading the action and outcome with no waste or repetition. It is appropriately sized for the amount of information it chooses to convey.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should ideally explain success/failure behavior or return semantics, but it only states the meaning of a valid signature. For a multi-step cryptographic proof step, prerequisites are implied by "step Q2" rather than fully stated.

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%, with all four parameters documented, including signature format and challenge_id source. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific action ("Send the signed challenge") and outcome ("proves you hold the key in the directory: step Q2"). It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as qagent_verify or qagent_status.

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?

"step Q2" implies this follows qagent_challenge, and the schema reinforces that challenge_id comes from qagent_challenge. However, the description gives no explicit when-to-use, when-not-to-use, or alternative 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