Skip to main content
Glama

portal_bitcoin_query_transactions

Query raw Bitcoin transactions with optional inline inputs and outputs. Filter by block range or timeframe, up to 200 transactions.

Instructions

Query raw Bitcoin transactions and optionally attach inputs and outputs inline.

COMMON USER ASKS:

  • Recent Bitcoin transactions

  • Attach inputs and outputs

WHEN TO USE:

  • You need raw Bitcoin transaction records.

  • You want the UTXO envelope without switching to separate input/output tools.

DON'T USE:

  • You only need a quick wallet or network summary.

EXAMPLES:

  • Recent Bitcoin transactions: {"network":"bitcoin-mainnet","timeframe":"1h","limit":20}

  • Attach inputs and outputs: {"network":"bitcoin-mainnet","timeframe":"1h","include_inputs":true,"include_outputs":true,"limit":10}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax transactions to return (default: 50, max: 200)
cursorNoContinuation cursor from a previous response
networkNoNetwork name (default: bitcoin-mainnet). Optional when continuing with cursor.
to_blockNoEnding block number
timeframeNoTime range (e.g., '1h', '24h'). Alternative to from_block/to_block.
from_blockNoStarting block number
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
finalized_onlyNoOnly query finalized blocks
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
include_inputsNoAttach transaction inputs inline
include_outputsNoAttach transaction outputs inline
response_formatNoResponse format: defaults to 'compact' for chat-friendly output. Compact mode keeps inline inputs and outputs in a smaller shape when requested.
Behavior4/5

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

No annotations exist, so description carries full burden. It clearly implies read-only querying, describes optional inline input/output attachment, and mentions response format options (compact mode). However, it does not explicitly state non-destructive nature or discuss pagination limits beyond cursor.

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?

Well-structured with clear sections: main action, common asks, when/don't use, examples. Front-loaded with key purpose. Examples add length but are instructional. Minor redundancy in common asks section.

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?

Covers usage context well with examples and guidelines. However, no output schema is provided, and the description only mentions 'UTXO envelope' without detailing the response structure. Pagination behavior beyond cursor parameter is not explained, leaving some gaps for a tool with 12 optional parameters.

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 description coverage is high (100%), so baseline is 3. The description adds value through examples showing parameter combinations and explaining behavior like 'Compact mode keeps inline inputs and outputs in a smaller shape,' but does not introduce new semantic meaning beyond the schema.

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 'Query raw Bitcoin transactions' with a specific verb and resource. It distinguishes from sibling tools like portal_evm_query_transactions by specifying Bitcoin and focusing on raw transaction records including UTXO envelopes.

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?

Provides distinct WHEN TO USE and DON'T USE sections. Explicitly warns against using for wallet/network summaries, implicitly directing to alternatives like portal_get_wallet_summary. Examples illustrate common use cases and parameter combinations.

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/subsquid-labs/portal-mcp-server'

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