SQD

Official

by subsquid-labs

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Find Bitcoin transactions

portal_bitcoin_query_transactions

Read-only

Retrieve raw Bitcoin transactions by time range or block range, with optional inline inputs and outputs for complete UTXO data in a single query.

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

Name	Required	Description
`limit`	No	Max transactions to return (default: 50, max: 200)
`cursor`	No	Continuation cursor from a previous response
`network`	No	Network name (default: bitcoin-mainnet). Optional when continuing with cursor.
`to_block`	No	Ending block number
`timeframe`	No	Time range (e.g., '1h', '24h'). Alternative to from_block/to_block.
`from_block`	No	Starting block number
`to_timestamp`	No	Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
`finalized_only`	No	Only query finalized blocks
`from_timestamp`	No	Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
`include_inputs`	No	Attach transaction inputs inline
`include_outputs`	No	Attach transaction outputs inline
`response_format`	No	Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps inline inputs and outputs in a smaller shape when requested.

Output Schema

TableJSON Schema

Name	Required	Description
`_ui`	No	Optional chart, table, and follow-up presentation metadata.
`_llm`	No	Hints that help an AI client locate the primary evidence.
`_meta`	No	Network, block range, timing, and row-count metadata.
`error`	No	Structured failure details when the tool cannot complete the request.
`items`	No	Primary result rows when the tool returns a list.
`value`	No	Primary result when the tool returns a scalar value.
`answer`	No	Concise answer grounded in the returned blockchain data.
`_notice`	No	Important limitation or truncation notice.
`display`	No	Plain-language labels for presenting the result.
`_notices`	No	Important limitations or truncation notices.
`_summary`	No	Human-readable summary of the result.
`_coverage`	No	Completeness of the requested window and result set.
`_evidence`	No	Replayable arguments, exact-data digest, row count, and completeness receipt.
`_ordering`	No	Ordering guarantees for the returned data.
`_execution`	No	Bounded execution and scan details.
`_freshness`	No	Freshness and finality information for the returned data.
`next_steps`	No	Safe follow-up actions and continuation guidance.
`_pagination`	No	Pagination state and an optional continuation cursor.
`investigation`	No	Evidence paths, useful pivots, and result limitations.
`pipes_handoff`	No	Optional SQD Pipes guidance for custom data needs.
`_tool_contract`	No	Tool identity, intent, and supported blockchain families.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedv0.8.3Aug 30, 2026

addedOutput schema / properties / _evidence

Added value: +{
+  "additionalProperties": {},
+  "description": "Replayable arguments, exact-data digest, row count, and completeness receipt.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed7 schema fields changedv0.8.2Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / from_timestamp / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / from_timestamp / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

addedInput schema / properties / to_timestamp / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / to_timestamp / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_coverage": {
+      "description": "Completeness of the requested window and result set."
+    },
+    "_execution": {
+      "additionalProperties": {},
+      "description": "Bounded execution and scan details.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_freshness": {
+      "description": "Freshness and finality information for the returned data."
+    },
+    "_llm": {
+      "description": "Hints that help an AI client locate the primary evidence."
+    },
+    "_meta": {
+      "additionalProperties": {},
+      "description": "Network, block range, timing, and row-count metadata.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_notice": {
+      "description": "Important limitation or truncation notice.",
+      "type": "string"
+    },
+    "_notices": {
+      "description": "Important limitations or truncation notices.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "_ordering": {
+      "description": "Ordering guarantees for the returned data."
+    },
+    "_pagination": {
+      "additionalProperties": {},
+      "description": "Pagination state and an optional continuation cursor.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_summary": {
+      "description": "Human-readable summary of the result.",
+      "type": "string"
+    },
+    "_tool_contract": {
+      "additionalProperties": {},
+      "description": "Tool identity, intent, and supported blockchain families.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_ui": {
+      "description": "Optional chart, table, and follow-up presentation metadata."
+    },
+    "answer": {
+      "description": "Concise answer grounded in the returned blockchain data.",
+      "type": "string"
+    },
+    "display": {
+      "additionalProperties": {},
+      "description": "Plain-language labels for presenting the result.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": {},
+      "description": "Structured failure details when the tool cannot complete the request.",
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "origin": {
+          "type": "string"
+        },
+        "retry_after_ms": {
+          "type": "number"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "suggestions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "origin",
+        "summary",
+        "retryable",
+        "suggestions"
+      ],
+      "type": "object"
+    },
+    "investigation": {
+      "additionalProperties": {},
+      "description": "Evidence paths, useful pivots, and result limitations.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "items": {
+      "description": "Primary result rows when the tool returns a list.",
+      "items": {},
+      "type": "array"
+    },
+    "next_steps": {
+      "additionalProperties": {},
+      "description": "Safe follow-up actions and continuation guidance.",
+      "properties": {
+        "actions": {
+          "items": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "continuation": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "custom_data": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "actions"
+      ],
+      "type": "object"
+    },
+    "pipes_handoff": {
+      "description": "Optional SQD Pipes guidance for custom data needs."
+    },
+    "value": {
+      "description": "Primary result when the tool returns a scalar value."
+    }
+  },
+  "type": "object"
+}

First observedv0.7.9Jun 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context by mentioning raw transaction records, optional inline inputs/outputs, and the UTXO envelope, which informs the agent about the response shape without relying solely on schema.

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?

The description is well-organized with clear section labels and immediately front-loads the main purpose. Some redundancy exists between COMMON USER ASKS and EXAMPLES, but overall it remains concise and scannable.

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 12-parameter read-only query tool with full schema descriptions and an output schema, the description covers the key use cases, exclusions, and example invocations. It does not discuss cursor pagination or all time-filter options, but those are documented in the schema, so the description remains sufficient.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds value through examples combining network, timeframe, limit, include_inputs, and include_outputs, but it does not go beyond what the schema already documents for other parameters.

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 the tool's function: 'Query raw Bitcoin transactions' with optional inline inputs and outputs. It distinguishes itself from sibling tools by specifying Bitcoin network raw transaction records and the UTXO envelope, making it unambiguous.

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?

The WHEN TO USE and DON'T USE sections give explicit guidance on when to use the tool versus when to avoid it, such as for wallet/network summaries. It does not name specific sibling tools, but points clearly toward the relevant alternative use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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