Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Quantum Agent Directory

qagent_directory
Read-only

Look up agents that upgraded to quantum agents: level, operator, post-quantum key fingerprint and certificate. Use it before trusting or paying another agent. Paid per call via x402 when payments are on (see quantum_pricing).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qagent_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOnly this level: quantum_agent_plus, quantum_agent, quantum_safe_identity, quantum_aware, enrolled
limitNo
queryNoSearch by agent or operator name

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 already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely new information: the tool is a paid, per-call x402 endpoint when payments are enabled, with a pointer to quantum_pricing. It does not specify pagination or error behaviour, but the metered-cost disclosure is exactly the kind of context annotations cannot carry.

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 tight sentences, front-loaded with the action and followed by the decision rule and the payment caveat. Nothing is repeated and no filler is present.

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 usefully names the fields returned (certificate, key fingerprint), and it flags the payment gate with a sibling pointer. Only the undocumented limit parameter and the absence of alternative-lookup guidance keep it from being fully complete.

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 67%: level and query are documented in the schema, and the description adds no filtering syntax or semantics beyond them. The 'level' list in the description mirrors the schema's level description rather than extending it, and limit remains undocumented in both places, so this is baseline territory.

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 states a specific verb and resource ('Look up agents that upgraded to quantum agents') and enumerates the returned fields (level, operator, post-quantum key fingerprint, certificate). It does not explicitly distinguish itself from close siblings such as qagent_status or privilege_directory, so it falls short of a 5.

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?

'Use it before trusting or paying another agent' gives a concrete decision context for calling the tool. It does not name alternative lookups (qagent_status, qagent_verify) or state when not to use it, so it is clear but not exhaustive.

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