Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Quantum Agent: enroll

qagent_enroll

Join the Quantum Agent Accelerator. Returns agent_id and agent_token (shown once; keep it) and your upgrade plan. Your public key goes in the directory so other agents can verify what you sign. Paid per call via x402 when payments are on (see quantum_pricing).

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": {
      "name": "<name>",
      "operator": "<operator>",
      "public_key": "<public_key>"
    },
    "name": "qagent_enroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesYour agent's name
listedNoShow this agent in the public Quantum Agent Directory
homepageNoOptional https:// page about the agent
operatorYesThe company or person accountable for this agent
public_keyYesBase64 of your raw ML-DSA-44/65/87 public key (FIPS 204). accelerator_info shows how to make one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-idempotent, closed-world), the description discloses two behaviors an agent could not otherwise know: the token is shown only once and must be retained, and the public key is published into a directory other agents read. It also flags the x402 pay-per-call path, though it defers actual pricing to quantum_pricing rather than stating any cost or failure mode.

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?

Short and front-loaded with the outcome, then the token caveat, then the key-visibility note, then payment. Slightly run-on in places ("Returns agent_id and agent_token (shown once; keep it) and your upgrade plan") but every clause carries information and none is filler.

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 correctly compensates by naming the return values and warning that the token is single-display. It covers key format, directory exposure, and payment routing. The remaining gap is whether re-enrollment is possible or what happens on duplicate name/operator, which matters for a non-idempotent mutation.

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%, so all five parameters already carry their own descriptions, including the key format (base64 ML-DSA-44/65/87) and the listed-visibility toggle. The description adds only a light restatement that the public key becomes directory-visible; it contributes no new meaning about name, operator, or homepage. Baseline 3 applies when the schema does the heavy lifting.

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 ("Join the Quantum Agent Accelerator") and spells out what the call produces: agent_id, agent_token, and an upgrade plan. It is clearly distinguishable from siblings such as accelerator_info (informational) and qagent_status (post-enrollment lookup).

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?

Implied and partly stated context is strong: accelerator_info is named as the place to learn key generation, and quantum_pricing is named for the payment side. What is missing is an explicit statement of when this should be called versus re-called (e.g., one enrollment per operator, how to handle an existing agent_id), leaving the agent to infer the lifecycle.

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