Skip to main content
Glama

scan_post_quantum

Check whether a domain's TLS is using post-quantum (hybrid ML-KEM) key exchange. Verdicts come from the open-source FEDLIN PQC Toolkit's published ruleset, under the civilian (NIST) or nss (CNSA 2.0) profile.

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": {
      "domain": "<domain>"
    },
    "name": "scan_post_quantum"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA bare public hostname to scan, for example example.com. No scheme, path, or port; IP literals and internal hostnames are rejected.
profileNoVerdict profile: civilian (NIST FIPS 203/204/205 and IR 8547, the default) or nss (national security systems, CNSA 2.0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / profile
      Added value: +{
      +  "description": "Verdict profile: civilian (NIST FIPS 203/204/205 and IR 8547, the default) or nss (national security systems, CNSA 2.0).",
      +  "enum": [
      +    "civilian",
      +    "nss"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It usefully discloses verdict provenance (the open-source FEDLIN PQC Toolkit published ruleset) and the meaning of the two profiles, which is real behavioral context. It omits other important traits: whether the scan is an active outgoing network connection, expected latency, failure behavior, or that it is a read-only operation.

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 sentences, front-loaded with the core purpose and followed by the provenance/profile note. Every clause carries information; there is no filler or repetition.

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?

For a two-parameter read tool with a fully documented schema, the description covers purpose and verdict origin adequately. With no output schema, though, the caller gets no sense of the return shape beyond the word 'verdict' — no fields, statuses, or result granularity — which is a meaningful gap for a scanner whose entire value is its result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters (domain constraints, profile enum with default) are fully documented in the schema, so the baseline of 3 applies only if the description adds nothing contradictory. The description does restate the civilian/nss profile distinction with the NIST vs CNSA 2.0 standards mapping already present in the schema, adding no new semantics, so it sits slightly below the baseline.

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 uses a specific verb ('Check whether') tied to a precise resource ('a domain's TLS ... post-quantum (hybrid ML-KEM) key exchange'), so an agent knows exactly what question this tool answers. It does not explicitly contrast itself with sibling scanners like scan_domain_trust or scan_security_headers, but the narrow subject matter makes it distinguishable in practice.

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?

Usage is implied by the domain+TLS framing, and the mention of two verdict profiles hints at a choice the caller must make. However, there is no explicit when-to-use / when-not-to-use statement and no routing to alternative scan tools, leaving the agent to infer the boundary itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources