SQD

Chart blockchain activity

portal_get_time_series

Read-only

Build simple activity charts and other time-series views across supported VMs, including compare-previous windows and grouped EVM contract trends.

COMMON USER ASKS:

Base transactions per 15m bucket
Compare two periods

FIRST CHOICE FOR:

activity over time, compare-current-vs-previous, grouped trends, and simple activity charts

WHEN TO USE:

You want chart-ready metric buckets over time.
You want a simple activity chart for a network, defaulting to a 6h interactive window unless a longer window is explicitly requested.
You want to compare the current period to the previous period.

DON'T USE:

You need raw record lists instead of aggregated buckets.
You need DEX pool candles or OHLC output.

EXAMPLES:

Base transactions per 15m bucket: {"network":"base-mainnet","metric":"transaction_count","duration":"6h","interval":"15m"}
Compare two periods: {"network":"solana-mainnet","metric":"transaction_count","duration":"1h","interval":"5m","compare_previous":true}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.	deep
`metric`	Yes	Metric to aggregate over time. Per chain family: evm: transaction_count, transactions_per_block, avg_gas_price, gas_used, block_utilization, unique_addresses; solana: transaction_count, unique_addresses, tps, avg_fee, success_rate, slots_per_hour; bitcoin: transaction_count, unique_addresses, fees_btc, block_size_bytes; hyperliquid: volume, fill_count, unique_traders. Others are refused.
`address`	No	Optional: Filter to specific contract address for contract-specific trends
`network`	Yes	Network name (supports short names: 'ethereum', 'polygon', 'base', etc.)
`duration`	No	Total time period to analyze. Defaults to "6h" for interactive use. The bound is in blocks, not time: this tool reads every block in the window and stops at 12,000, so "24h" is fine on Bitcoin or Ethereum and refused on a 2-second chain like Base (43,200 blocks). A window over the bound is refused at once and the error names a duration that fits. Accepts compact durations like "30m" or natural phrases like "past 30 minutes".	6h
`group_by`	No	Optional grouping mode. contract is currently supported only for EVM transaction_count	none
`interval`	Yes	Time bucket interval (5m, 15m, 1h, 6h, 1d)
`group_limit`	No	Maximum number of contract groups when group_by=contract
`to_timestamp`	No	Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
`from_timestamp`	No	Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "24h ago".
`compare_previous`	No	Compare the selected window against the immediately previous window

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.

Changed53 schema fields changedSep 7, 2026

changedInput schema / properties / duration / description

Previous value: -"Total time period to analyze. Defaults to \"6h\" for interactive use. Explicit longer windows like \"24h\" or \"7d\" are supported but can take longer. Accepts compact durations like \"30m\" or natural phrases like \"past 30 minutes\"."New value: +"Total time period to analyze. Defaults to \"6h\" for interactive use. The bound is in blocks, not time: this tool reads every block in the window and stops at 12,000, so \"24h\" is fine on Bitcoin or Ethereum and refused on a 2-second chain like Base (43,200 blocks). A window over the bound is refused at once and the error names a duration that fits. Accepts compact durations like \"30m\" or natural phrases like \"past 30 minutes\"."

changedInput schema / properties / metric / description

Previous value: -"Metric to aggregate over time"New value: +"Metric to aggregate over time. Per chain family: evm: transaction_count, transactions_per_block, avg_gas_price, gas_used, block_utilization, unique_addresses; solana: transaction_count, unique_addresses, tps, avg_fee, success_rate, slots_per_hour; bitcoin: transaction_count, unique_addresses, fees_btc, block_size_bytes; hyperliquid: volume, fill_count, unique_traders. Others are refused."

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

Changed1 schema field changedAug 31, 2026

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.8/5.0

Behavior5/5

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

Annotations already mark this read-only and non-destructive, and the description adds behavioral context beyond them: it returns aggregated chart-ready metric buckets rather than raw records, defaults to a 6h interactive window, and supports compare-previous and grouped EVM contract trends. No contradiction with annotations.

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 headers, front-loaded purpose, and scannable sections. Slight redundancy exists because COMMON USER ASKS overlaps with EXAMPLES, and FIRST CHOICE FOR largely repeats WHEN TO USE, but the repetition is not harmful.

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?

For an 11-parameter tool with a fully described schema and an output schema, the description is complete: it covers purpose, use cases, exclusions, defaults, and concrete examples. An agent has everything needed to select and construct a valid call.

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; the description earns a 4 by mapping common user asks to concrete payloads (e.g., Base transactions per 15m bucket and compare-two-periods examples). This adds usable meaning about parameter combinations beyond the bare schema definitions.

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 specific purpose: building simple activity charts and time-series views from aggregated metric buckets across supported VMs. The DON'T USE section distinguishes it from raw record-list and OHLC tools, so it is clearly differentiated from siblings.

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 explicit WHEN TO USE and DON'T USE sections, naming the conditions that select this tool (chart-ready buckets, compare-current-vs-previous, grouped trends) and the conditions that rule it out (raw record lists, OHLC/DEX candles). It also calls itself FIRST CHOICE FOR the relevant scenarios, leaving little to inference.

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.