SQD

by io.github.subsquid-labs

Overview Discussions Admin

Find Bitcoin transactions

portal_bitcoin_query_transactions

Read-only

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: 20, max: 25). With include_inputs or include_outputs and response_format "full", a page near the maximum can exceed the 50,000-byte response budget; the response_too_large error then names the limit to retry with.
`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	Chart, table, and follow-up presentation metadata.
`_app`	No	SQD Explorer identity and host-render state.
`_llm`	No	Hints to locate the primary evidence.
`_meta`	No	Network, block range, timing, and row counts.
`error`	No	Structured failure details.
`items`	No	Primary rows for list results.
`value`	No	Primary scalar result.
`answer`	No	Answer grounded in the returned data.
`_notice`	No	Limitation or truncation notice.
`_server`	No	SQD server name, exact version, and git commit.
`display`	No	Labels for presenting the result.
`_notices`	No	Limitation or truncation notices.
`_summary`	No	Human-readable summary.
`_coverage`	No	Window and result completeness.
`_evidence`	No	Replayable arguments, digest, row count, and receipt.
`_ordering`	No	Ordering guarantees.
`_execution`	No	Bounded execution and scan details.
`_freshness`	No	Freshness and finality.
`next_steps`	No	Safe follow-up actions and continuation guidance.
`_pagination`	No	Pagination state and next_cursor.
`investigation`	No	Evidence paths, pivots, and limitations.
`pipes_handoff`	No	SQD Pipes guidance for custom data needs.
`_tool_contract`	No	Tool identity, intent, and chain families.

Schema Changelog

Changes observed during successful MCP inspections.

Changed52 schema fields changedSep 7, 2026

changedInput schema / properties / limit / description

Previous value: -"Max transactions to return (default: 20, max: 25)"New value: +"Max transactions to return (default: 20, max: 25). With include_inputs or include_outputs and response_format \"full\", a page near the maximum can exceed the 50,000-byte response budget; the response_too_large error then names the limit to retry with."

removedOutput schema / properties / _app / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / _app / description

Previous value: -"SQD Explorer identity and honest host-render state."New value: +"SQD Explorer identity and host-render state."

removedOutput schema / properties / _app / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _app / type
```
Removed value: -"object"
```

changedOutput schema / properties / _coverage / description

Previous value: -"Completeness of the requested window and result set."New value: +"Window and result completeness."

removedOutput schema / properties / _evidence / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / _evidence / description

Previous value: -"Replayable arguments, exact-data digest, row count, and completeness receipt."New value: +"Replayable arguments, digest, row count, and receipt."

removedOutput schema / properties / _evidence / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _evidence / type
```
Removed value: -"object"
```
removedOutput schema / properties / _execution / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / _execution / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _execution / type
```
Removed value: -"object"
```

changedOutput schema / properties / _freshness / description

Previous value: -"Freshness and finality information for the returned data."New value: +"Freshness and finality."

changedOutput schema / properties / _llm / description

Previous value: -"Hints that help an AI client locate the primary evidence."New value: +"Hints to locate the primary evidence."

removedOutput schema / properties / _meta / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / _meta / description

Previous value: -"Network, block range, timing, and row-count metadata."New value: +"Network, block range, timing, and row counts."

removedOutput schema / properties / _meta / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _meta / type
```
Removed value: -"object"
```

changedOutput schema / properties / _notice / description

Previous value: -"Important limitation or truncation notice."New value: +"Limitation or truncation notice."

changedOutput schema / properties / _notices / description

Previous value: -"Important limitations or truncation notices."New value: +"Limitation or truncation notices."

changedOutput schema / properties / _ordering / description

Previous value: -"Ordering guarantees for the returned data."New value: +"Ordering guarantees."

removedOutput schema / properties / _pagination / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / _pagination / description

Previous value: -"Pagination state and an optional continuation cursor."New value: +"Pagination state and next_cursor."

removedOutput schema / properties / _pagination / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _pagination / type
```
Removed value: -"object"
```

changedOutput schema / properties / _server / description

Previous value: -"Observable SQD server identity and exact release version."New value: +"SQD server name, exact version, and git commit."

addedOutput schema / properties / _server / properties / commit
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / _server / required

Previous value: -[
-  "name",
-  "version"
-]New value: +[
+  "name",
+  "version",
+  "commit"
+]

changedOutput schema / properties / _summary / description

Previous value: -"Human-readable summary of the result."New value: +"Human-readable summary."

removedOutput schema / properties / _tool_contract / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / _tool_contract / description

Previous value: -"Tool identity, intent, and supported blockchain families."New value: +"Tool identity, intent, and chain families."

removedOutput schema / properties / _tool_contract / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _tool_contract / type
```
Removed value: -"object"
```

changedOutput schema / properties / _ui / description

Previous value: -"Optional chart, table, and follow-up presentation metadata."New value: +"Chart, table, and follow-up presentation metadata."

changedOutput schema / properties / answer / description

Previous value: -"Concise answer grounded in the returned blockchain data."New value: +"Answer grounded in the returned data."

removedOutput schema / properties / display / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / display / description

Previous value: -"Plain-language labels for presenting the result."New value: +"Labels for presenting the result."

removedOutput schema / properties / display / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / display / type
```
Removed value: -"object"
```

changedOutput schema / properties / error / description

Previous value: -"Structured failure details when the tool cannot complete the request."New value: +"Structured failure details."

removedOutput schema / properties / investigation / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / investigation / description

Previous value: -"Evidence paths, useful pivots, and result limitations."New value: +"Evidence paths, pivots, and limitations."

removedOutput schema / properties / investigation / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / investigation / type
```
Removed value: -"object"
```

changedOutput schema / properties / items / description

Previous value: -"Primary result rows when the tool returns a list."New value: +"Primary rows for list results."

removedOutput schema / properties / next_steps / additionalProperties
```
Removed value: -{}
```

removedOutput schema / properties / next_steps / properties

Removed value: -{
-  "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"
-  }
-}

removedOutput schema / properties / next_steps / required
```
Removed value: -[
-  "actions"
-]
```
removedOutput schema / properties / next_steps / type
```
Removed value: -"object"
```

changedOutput schema / properties / pipes_handoff / description

Previous value: -"Optional SQD Pipes guidance for custom data needs."New value: +"SQD Pipes guidance for custom data needs."

changedOutput schema / properties / value / description

Previous value: -"Primary result when the tool returns a scalar value."New value: +"Primary scalar result."

Changed2 schema fields changedSep 1, 2026

changedOutput schema / properties / _app / description

Previous value: -"SQD Blockchain Activity Explorer identity and honest host-render state."New value: +"SQD Explorer identity and honest host-render state."

addedOutput schema / properties / _server

Added value: +{
+  "additionalProperties": false,
+  "description": "Observable SQD server identity and exact release version.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedAug 31, 2026

changedInput schema / properties / limit / default
```
Previous value: -50New value: +20
```

changedInput schema / properties / limit / description

Previous value: -"Max transactions to return (default: 50, max: 200)"New value: +"Max transactions to return (default: 20, max: 25)"

changedInput schema / properties / limit / maximum
```
Previous value: -200New value: +25
```

addedOutput schema / properties / _app

Added value: +{
+  "additionalProperties": {},
+  "description": "SQD Blockchain Activity Explorer identity and honest host-render state.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 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"
+}

Changed1 schema field changedAug 28, 2026

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"
+}

Changed6 schema fields changedAug 27, 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"
-]
```

First observedJun 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the tool read-only and non-destructive. The description adds useful context about returning raw transactions, optionally attaching inputs/outputs inline, and avoiding separate input/output tools. It does not discuss pagination or response size limits, but those are already documented in the schema and output schema.

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?

The one-sentence summary is front-loaded, followed by compact, scannable sections for common asks, when to use, don't use, and examples. Every section earns its place with no redundant filler.

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?

Given the tool's 12 optional parameters and rich schema/output schema, the description provides sufficient selection and invocation guidance: clear purpose, use cases, exclusions, and two example payloads. Remaining details like cursor pagination are already covered by the parameter descriptions.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is met. The description adds value with concrete example payloads showing realistic combinations of network, timeframe, limit, and include_inputs/include_outputs.

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?

States a clear verb and resource ('Query raw Bitcoin transactions') and specifies the optional inline input/output attachment. The 'raw' vs 'summary' distinction and UTXO envelope phrasing help differentiate it from summary/analytics tools.

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?

Includes explicit WHEN TO USE and DON'T USE sections, telling the agent to use it for raw transaction records or UTXO envelopes and to avoid it for quick wallet/network summaries. However, it does not explicitly name the alternative tools such as portal_get_wallet_summary or portal_bitcoin_get_analytics.

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

All SQD tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.