Skip to main content
Glama

Bitcoin Block Tip Payment Quote

bitcoin_tip_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/bitcoin/tip (base $0.002; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET with no parameters. Latest Bitcoin block (height, hash, time, age) from mempool.space® (cached), charged only when the tip is read and the block header hashes to that tip. Fee estimates in sat/vB reported by mempool.space when available; if fees are missing the tip is still charged, marked partial:true with fees null. Source down or a header mismatch: not charged. Not affiliated with or endorsed by Mempool Holdings S.A. de C.V. Fee estimates do not guarantee inclusion. Information only. USDC on Base or Polygon. On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (native USDC), a request is settled only when it succeeds (HTTP status below 400). Failed requests

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The description adds substantial behavior beyond the annotations: cached data, charge-only-on-successful-header-hash, partial:true with null fees when estimates are missing, and per-chain settlement rules (Base, Polygon, Solana, XRP Ledger). Annotations already declare readOnlyHint and destructiveHint=false and idempotentHint=true, so the safety profile is covered and the description's contribution is the billing/settlement nuance. The one tension is openWorldHint=false while the description cites external mempool.space data and a live URL, which an agent may read as an open-world call; the description does not resolve that ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the paragraph is bloated and disorganized: 'USDC on Base or Polygon' appears twice, legal disclaimers about Mempool Holdings sit mid-description, and the text ends mid-sentence with 'Failed requests'. Billing exceptions across four chains crowd out the single most important fact, which is the quote amount and the fact that calling it is free.

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?

There is no output schema, so the description must carry the return semantics, and it partially does by describing the quote as payment terms plus cached block data plus fee estimates. However, it never states the shape of what is returned (price, currency, chain, expiry) or how long a quote is valid, and the truncated final sentence leaves the error-charging policy incomplete. For a tool whose entire output is the untyped quote object, that is a real gap.

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?

Zero parameters with 100% schema coverage, so there is nothing for the description to compensate for; it correctly confirms 'GET with no parameters.' Baseline for a parameterless tool applies and the explicit no-parameter statement is a small bonus.

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?

Names a specific verb and resource: returns payment terms for a specific endpoint, with a base price and accepted chains, then explicitly scopes itself with 'this tool never runs the check or pays.' That last clause distinguishes it from actually executing the paid lookup, which is the key confusion risk for a quote tool. It does not differentiate from the many sibling *_quote tools, but those are structurally parallel, so the gap is minor.

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?

Gives clear operational context: GET with no parameters, pay the 402 over HTTP with x402 v2, and the tool itself will not perform the fetch or payment. That tells an agent what to do before and after calling it. It stops short of explicit when-not-to-use guidance or naming an alternative, so it is not a 5.

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.