Skip to main content
Glama

hndl_exposure

Scan an account's transaction history to detect if its signing public key has been revealed on-ledger, classifying the key as irreversible, recoverable, or never exposed, and report balance at risk.

Instructions

Measure an account's Harvest-Now-Decrypt-Later exposure: has its signing PUBLIC KEY been revealed on-ledger, and which key? An r-address is a HASH of the pubkey; the pubkey is exposed only once the account signs a tx. Walks history OLDEST-first and classifies: master (IRREVERSIBLE — master key can't be rotated), regular / multisig (RECOVERABLE — rotate the key), or none (never signed = hash-only, not Shor-actionable). Reports balance-at-risk + honest truncation caveat. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesr-address
networkNomainnet
maxPagesNohistory pages to scan (default 6 × 400 tx)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
errorNo
addressNo
exposedNo
networkNo
scannedYes
severityNo
accountIdNo
conclusiveNo
recoverableNo
balanceDropsNo
exposureClassNo
masterExposedNo
signedTxCountNo
masterDisabledNo
regularExposedNo
multisigExposedNo
balanceAtRiskDropsNo
firstExposureLedgerNo
Behavior4/5

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

The description discloses the read-only nature, history traversal (oldest-first), classification logic, and the 'honest truncation caveat'. No annotations exist, so the description carries full burden. It does not mention potential performance impact of maxPages, but overall is transparent.

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?

The description is well-structured with front-loaded purpose and clear sentences. It avoids redundancy but could be slightly more compact. Each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description need not detail return values. It adequately covers the tool's behavior, classification outcomes, and caveats, making it complete for the tool's complexity.

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%, with descriptions on address (r-address), network (enum), and maxPages (history pages). The description adds no new parameter-specific details beyond the schema, only explaining the tool's output logic.

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 clearly states a specific verb ('Measure') and resource ('account's HNDL exposure'), with detailed explanation of classification types (master, regular, multisig, none). It distinguishes itself from sibling tools by focusing on post-quantum threat assessment rather than general account info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives (e.g., get_account_info for general data). The description implies usage for security assessment but lacks direct 'when to use' or 'when not to use' context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hugegreencandle/xahau-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server