Skip to main content
Glama

Ellimist

Quantum exposure index

quantum_exposure_index
Read-only

Use this to see how much tracked ETH sits in addresses whose public key is already revealed, and so would be exposed to a future quantum computer: daily index with history, shares of tracked balance (revealed, hidden, contract), counts and coverage. Aggregate only; no addresses. Price: $0.01 USDC per call via x402 (no account). Not charged if it fails.

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": "quantum_exposure_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNohistory to include
chainNoethereum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations only declare readOnlyHint and openWorldHint, so the description adds real operational context: cost of $0.01 USDC per call via x402, no account required, and no charge on failure. It also discloses the aggregate-only output granularity, which matters for planning. Remaining gaps are data freshness, latency, and any rate limits, which keeps it from a 5.

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?

One dense, front-loaded sentence that leads with the payoff (exposure to a future quantum computer) before listing the outputs and pricing terms. The clause 'counts and coverage' is slightly listy but each fragment carries information an agent needs. No filler or repetition of the title.

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 takes on the job of describing returns and does so concretely: daily index with history, revealed/hidden/contract balance shares, counts and coverage. Payment and failure semantics are also covered. It is only incomplete on freshness and per-chain scope, which are secondary for a two-parameter read-only index.

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 50%: `days` carries its own description and `chain` is an enum, so the schema already handles much of the meaning. The description adds 'daily index with history', which clarifies that `days` is a rolling daily history window, but it says nothing about what choosing ethereum vs base changes (coverage, tracked universe). Baseline 3 for a borderline half-documented schema.

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 names a concrete resource and metric: how much tracked ETH sits in addresses with already-revealed public keys, plus the daily index, balance shares, counts and coverage. That is far more specific than the title, and 'Aggregate only; no addresses' draws a clear boundary against address-level siblings like quantum_pq_exposure. It stops short of explicitly naming a sibling, so it lands at 4 rather than 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 this to see how much tracked ETH...' gives a direct condition for reaching for this tool, and 'Aggregate only; no addresses' implicitly steers away from it when per-address detail is needed. What is missing is an explicit alternative (e.g. use X for address-level exposure) and any exclusion beyond the aggregate-only note.

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