SQD

Review wallet activity

portal_get_wallet_summary

Read-only

Summarize wallet activity and fund flow with shared overview, asset movement, counterparties, evidence pivots, and follow-up filters across supported networks.

COMMON USER ASKS:

EVM wallet fund-flow triage
Solana wallet activity and fee flow

FIRST CHOICE FOR:

one-call wallet analysis across supported VMs
suspicious wallet triage, fund-flow direction, counterparties, and next evidence pivots before drilling into raw records

WHEN TO USE:

You want a single high-level answer about what one wallet has been doing and where value appears to move.
You want inbound/outbound flow, activity and asset-movement counterparties, largest movements within each asset, and exact next pivots before drilling into raw transactions or fills.
The user asks to investigate a suspicious wallet, stolen-funds path, exploit counterparty, or incident address.

DON'T USE:

You need every raw record with full chain-specific fields and no summarization.

EXAMPLES:

EVM wallet fund-flow triage: {"network":"base-mainnet","address":"0xabc...","timeframe":"24h"}
Solana wallet activity and fee flow: {"network":"solana-mainnet","address":"Vote111...","timeframe":"6h"}

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
`cursor`	No	Continuation cursor from a previous response
`address`	No	Wallet address to analyze. Optional when continuing with cursor.
`network`	No	Network name or alias. Optional when continuing with cursor.
`timeframe`	No	Look-back period as timeframe or block count. Examples: '1h', '24h', '7d', '3d', '1000'.	1000
`include_nfts`	No	Include NFT transfers (ERC721/1155)
`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 "1h ago".
`include_tokens`	No	Include ERC20 token transfers
`limit_per_type`	No	Requested items per category (default: 5). Values up to the retained compatibility maximum of 10 are accepted, while each category is safely capped at 4 rows and remains cursorable.
`response_format`	No	Response format: defaults to 'compact' for a readable wallet investigation. Use 'summary' for headline flow only or 'full' for all returned activity rows.

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.

Changed51 schema fields changedSep 7, 2026

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."

Changed4 schema fields changedSep 1, 2026

changedInput schema / properties / limit_per_type / description

Previous value: -"Max items per category (default: 5, max: 5). This verified ceiling keeps every wallet page within MCP client response budgets."New value: +"Requested items per category (default: 5). Values up to the retained compatibility maximum of 10 are accepted, while each category is safely capped at 4 rows and remains cursorable."

changedInput schema / properties / limit_per_type / maximum
```
Previous value: -5New value: +10
```

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

Changed6 schema fields changedAug 31, 2026

changedInput schema / properties / limit_per_type / default
```
Previous value: -10New value: +5
```

changedInput schema / properties / limit_per_type / description

Previous value: -"Max items per category (txs, tokens, nfts)"New value: +"Max items per category (default: 5, max: 5). This verified ceiling keeps every wallet page within MCP client response budgets."

addedInput schema / properties / limit_per_type / maximum
```
Added value: +5
```
addedInput schema / properties / limit_per_type / minimum
```
Added value: +1
```
changedInput schema / properties / limit_per_type / type
```
Previous value: -"number"New value: +"integer"
```

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": "string"
+  },
+  {
+    "type": "number"
+  }
+]

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

addedInput schema / properties / to_timestamp / anyOf

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

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

First observedJun 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses real behavioral details: mode semantics ('fast value is only for explicitly bounded previews' versus deep default), limit_per_type 'safely capped at 4 rows and remains cursorable' despite accepting up to 10, and response_format defaults ('compact' for readable investigation, 'summary' for headline flow, 'full' for all rows). These add genuine behavioral facts not present in the 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?

The description is well structured with clear headed sections (COMMON USER ASKS, FIRST CHOICE FOR, WHEN TO USE, DON'T USE, EXAMPLES) and every section adds value. It is slightly redundant — COMMON USER ASKS, FIRST CHOICE FOR, and WHEN TO USE restate the same core message in similar phrasing — but the repetition is organized enough that it reads as emphasis rather than noise.

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 output schema exists (so return values need no explanation), the description covers all operational context: pagination via cursor, cross-network support (EVM, Solana examples), optional vs required parameters (0 required), the fast/deep mode distinction, and the relationship to sibling raw-query tools. An agent has everything needed to call this correctly without opening other references.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description enriches it further: examples demonstrate actual usage (e.g., {"network":"base-mainnet","address":"0xabc...","timeframe":"24h"}), clarifies cursor semantics ('Optional when continuing with cursor' on address/network), and disambiguates tricky fields like limit_per_type (capped at 4 despite max 10) and response_format (defaults to 'compact').

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 uses a specific verb and resource ('Summarize wallet activity and fund flow with shared overview, asset movement, counterparties, evidence pivots, and follow-up filters across supported networks') and explicitly differentiates itself from sibling raw-query tools like portal_evm_query_transactions via 'before drilling into raw records' (DON'T USE: 'You need every raw record'). An agent can immediately tell this is the high-level aggregation tool versus the detailed query 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?

The WHEN TO USE and DON'T USE sections are explicit and actionable: use when 'You want a single high-level answer about what one wallet has been doing', avoid when 'You need every raw record with full chain-specific fields'. This names the alternative behavior (raw record drilling, handled by sibling query_* tools) and gives concrete example invocations for both EVM and Solana networks.

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.