Skip to main content
Glama

Ellimist

Post-quantum exposure score

quantum_pq_exposure
Read-only

Use this to score how exposed an Ethereum or Bitcoin wallet is to future quantum attacks (revealed public keys, address reuse, Taproot) with migration advice. Price: $0.02 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "address": "<address>"
    },
    "name": "quantum_pq_exposure"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.02 USDC x402 charge per call, no account required, and no charge on failure — details an agent needs before invoking a paid endpoint. It does not contradict the annotations.

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?

Two sentences with no filler; the capability and its factors come first, with billing as a trailing clarification. Nothing is redundant, though the parenthetical factor list is slightly dense.

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 one-parameter, read-only scoring tool with no output schema, the description covers what is returned at a high level (a score plus migration advice) and the cost. It is still thin on input expectations and on what the score's shape or scale is, which matters when no output schema exists.

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 description coverage is 0%, so the description must carry the burden for the single `address` field. It adds real meaning by implying the address is a wallet on Ethereum or Bitcoin, but never specifies accepted formats (0x hex vs. bech32/base58), whether checksummed input is required, or what happens with an unsupported chain.

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?

States a specific verb and resource — scoring a single wallet's exposure to future quantum attacks — and enumerates the concrete factors considered (revealed public keys, address reuse, Taproot) plus the deliverable (migration advice). The chains supported (Ethereum, Bitcoin) are named. It lacks an explicit contrast with the similarly named siblings such as quantum_exposure_index, so an agent must infer that this is per-wallet while that one is presumably an index.

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?

"Use this to score..." establishes the intended context and the single-address schema makes the per-wallet scope inferable, but there is no when-not guidance, no prerequisites, and no named alternative for portfolio-level or index-level questions. The pricing sentence is helpful but is commercial, not selection guidance.

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