Skip to main content
Glama

Bitcoin Stratigraphy Enterprise Data Engine & Agent Notary Hub

Query MCP Prices or Verify Payment Settlement

payment.get_info

Query MCP pricing parameters (action='query', the default) or verify authenticated settlement (action='settle' with a payment hash and either an L402 preimage or Base transaction hash). Use query for price discovery before calling paid tools; use settle to check payment status, not to issue an invoice. Macaroons and Lightning invoices are issued dynamically via HTTP 402 challenges with bounded expiration; operator-only admin operations are intentionally omitted. Live L402 Satoshi settlement: a configured NWC wallet issues the exact-priced Lightning invoice; paid execution requires confirmed incoming settlement and an invoice-bound payment proof. Handle HTTP 402, pay explicitly, then retry the identical request with Authorization: L402 :. Invoice creation alone is not payment; unavailable verification does not authorize execution.

Input Schema

NameRequiredDescriptionDefault
actionNoquery (default) discovers prices; settle verifies authenticated payment. Constraints: allowed values: query, settle. Example: "query".query
txHashNoBase mainnet transaction hash, accepted only after facilitator settlement of PAYMENT-SIGNATURE. Constraints: pattern: ^0x[0-9a-fA-F]{64}$. Example: "0xabababababababababababababababababababababababababababababababab".
preimageNoOptional L402 preimage, NWC_LOOKUP, or UUID hint; the issued macaroon and exact merchant settlement remain required. Constraints: pattern: ^([0-9a-fA-F]{64}|[0-9a-fA-F]{8}(-[0-9a-fA-F]{4}){3}-[0-9a-fA-F]{12}|NWC_LOOKUP|nwc_lookup)$. Example: "cdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd".
toolNameNoOptional case-sensitive canonical MCP tool identifier (e.g., 'stratigraphy.get_digest' or 'proof.verify'); supported legacy aliases are also accepted and resolve to canonical names. When provided, filters output to return pricing specifically for that single tool. When omitted, returns the full pricing map across all registered catalog tools. Must match an exact registered tool name or supported legacy alias. Constraints: minLength: 1. Example: "stratigraphy.get_digest".
paymentHashNoL402 SHA-256 invoice hash, or Base tx hash when using x402. Constraints: pattern: ^(0x)?[0-9a-fA-F]{64}$. Example: "abababababababababababababababababababababababababababababababab".
paymentMacaroonNoOriginal invoice macaroon, separate from this tool's paid access credential. Constraints: minLength: 1; maxLength: 8192. Example: "eyJtYWNhcm9vbiI6ImV4YW1wbGUifQ".

Output Schema

NameRequiredDescriptionDefault
x402NoBase mainnet USDC x402 exact terms; present only when authenticated CDP settlement is configured.
verifiedNoWhether the signed, server-bound payment was verified or settled. Example: true.
challengeNoHTTP payment challenge and response fields.
perToolSatsNoCurrent advertised canonical tool prices in sats; optional toolName narrows this map.
settlementTokenNoVerified payment claims, not a bearer token or a grant of tool access.
activeAuthSchemesNoAuthentication schemes for paid MCP calls. Only stratigraphy.list and proof.list execute free. Example: ["L402"].
standardInvoiceSatsNoStandard paid MCP execution price. Catalog and status lookups may cost less; free tools cost zero. Example: 250.
wholesaleSubVendingNoWholesale purchase and delegated redemption capability metadata.
invoiceExpirySecondsNoDefault expiry for both the issued Lightning invoice and its path-bound macaroon. Constraints: minimum: 1. Example: 3600.
macaroonRequirementsNoA valid payment proof must match the bound invoice, provider, amount, path, expiry and request quota. proof.attenuate requires payment and a valid parent token.
_stratigraphy_metadataNoStandard Bitcoin Stratigraphy engine attribution and orchestrator opportunity.
acceptedPaymentMethodsNoSupported MCP payment method. Example: ["Lightning L402"].
agentSolvencyAttestationNoIssuer-signed historical settlement and live revocation telemetry for the queried pubkey.
upstreamVerificationAllocationsNoDurable allocation count and integer-millisatoshi totals for upstream verification allocation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say non-readonly, open-world, non-idempotent, non-destructive; the description adds substantial context — macaroons/invoices are issued via HTTP 402 with bounded expiration, an NWC wallet issues the exact-priced invoice, execution requires confirmed settlement, and unavailable verification does not authorize execution. It also discloses that operator-only admin operations are intentionally omitted.

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?

Mode selection is front-loaded in the first sentence, but the six-sentence block is dense and partially repetitive — macaroon/invoice issuance under HTTP 402 is restated in the settlement paragraph. Every sentence is relevant, though a couple could be tightened.

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?

With an output schema present, return values need not be explained; the description covers the remaining unknowns an agent needs — auth flow, proof requirements, and the warning that invoice creation alone is not payment. Nothing material for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds the coupling rule that settle needs a payment hash plus either a preimage or a Base tx hash, and that preimage is optional while the macaroon remains required. It does not deepen `toolName` filtering or `paymentMacaroon` beyond what the schema already states.

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 opening sentence names both modes precisely: query MCP pricing parameters (default) versus verify authenticated settlement with a payment hash plus L402 preimage or Base tx hash. An agent can distinguish the two operations and their required inputs without opening the schema, and no sibling tool overlaps this resource.

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

Usage Guidelines5/5

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

Explicit routing is given: use `query` for price discovery before calling paid tools, use `settle` to check payment status, and the exclusion 'not to issue an invoice' is stated outright. It also prescribes the operational sequence (handle HTTP 402, pay explicitly, retry with Authorization header).

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