Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Check public endpoints for post-quantum TLS

pqc_endpoint_check
Read-onlyIdempotent

Test live public sites and services for TLS 1.3 and hybrid post-quantum key exchange (X25519MLKEM768, FIPS 203), the protection against 'harvest now, decrypt later'. Sends two TLS hellos per endpoint and no data. Returns a status and fix per endpoint plus CBOM-ready assets for pqc_readiness_package. 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": {
      "endpoints": "<endpoints>"
    },
    "name": "pqc_endpoint_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointsYesPublic hostnames or URLs (up to 20), optionally with a TLS port, e.g. ['www.irs.gov', 'login.gov:443']

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the probe mechanics ('sends two TLS hellos per endpoint and no data'), the return shape (status and fix per endpoint plus CBOM-ready assets), and the billing model (paid per call via x402 when payments are on). Those are exactly the behavioral traits an agent cannot infer from readOnlyHint/openWorldHint/idempotentHint.

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?

Three sentences, front-loaded with purpose and then behavior and billing; nothing is padding. Minor inefficiency: the mid-sentence line break inside the parenthetical and the product-name plural make the first sentence slightly denser than needed.

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-value burden and does so ('status and fix per endpoint plus CBOM-ready assets'), and it flags the x402 payment gate. It stops short of stating failure behavior, such as unreachable endpoints or timeouts, on a tool that is inherently network-facing (openWorldHint).

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%: the endpoints array, the 20-item cap, and the optional TLS port example are all documented in the schema itself. The description adds no additional constraint on the parameter, so the baseline 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 opens with a concrete verb and resource: 'Test live public sites and services for TLS 1.3 and hybrid post-quantum key exchange (X25519MLKEM768, FIPS 203)', which tells an agent exactly what is being measured. The 'live public sites' scope implicitly separates it from pqc_scan_code and pqc_crypto_inventory, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

It supplies the motivating condition ('protection against harvest now, decrypt later') and the downstream consumer ('CBOM-ready assets for pqc_readiness_package'), plus a pointer to quantum_pricing for payment details. There is no explicit when-not guidance (e.g., don't use on internal hosts or source code), which keeps it a step below full 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