Skip to main content
Glama

premium_key_report

PAID (x402, $0.01 real USDC on Base mainnet). Verified key report for up to 10 agents: independent fingerprint recompute, cross-check of directory vs keys endpoint, revocation history, profile and a consistency verdict. Call without payment to get the x402 PaymentRequired; retry with the payment in _meta["x402/payment"].

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": {
      "names": "<names>"
    },
    "name": "premium_key_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes
expected_fingerprintsNoOptional map name -> fingerprint you learned out-of-band

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?

With no annotations, the description carries the full burden and does well: it discloses the cost and currency ($0.01 real USDC on Base mainnet), the protocol round-trip required before success, and the 10-agent scope. Gaps remain around failure modes — unknown names, partial-result behavior, or whether a failed report still charges — which matter for a paid tool.

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, both front-loaded: what you get and what it costs first, then exactly how to complete payment. The pricing, protocol trigger, and _meta key are each stated once with no padding.

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?

For a paid, no-annotation, no-output-schema tool, the description covers cost, payment protocol, scope, and the shape of the returned report. Missing are error semantics (nonexistent names, partial batches) and how the consistency verdict is expressed, but the core is sufficient to invoke correctly.

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 coverage is only 50%, and the description adds nothing about either parameter. 'Up to 10 agents' merely restates maxItems:10, and expected_fingerprints — the one parameter whose purpose (out-of-band comparison) drives the 'consistency verdict' — is never mentioned in the description. With low coverage, compensation was required and none is provided.

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 first sentence names a specific artifact and enumerates its contents (fingerprint recompute, cross-check, revocation history, profile, verdict) for a bounded resource (up to 10 agents). It distinguishes itself from free siblings only implicitly via 'Verified'/'cross-check' — no sibling is named, so an agent must infer the difference from lookup_keys_batch or verify_signature.

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?

The payment flow ('Call without payment to get the x402 PaymentRequired; retry with payment') is excellent invocation guidance, but it addresses how to pay, not when to choose this tool over lookup_keys_batch or verify_signature. The condition that selects a paid verified report over the free lookups is left implicit.

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