whale-insights

bridge_flows

Read-onlyIdempotent

Get recent large cross-chain bridge transfers — Stargate Finance, Socket/Bungee via LI.FI (top 3 free; capital-rotation signal) — Recent large cross-chain bridge transfers and per-bridge volume summaries sourced from LI.FI. Free preview: top 3 flows + 2 bridge summaries; the full flow history requires a Weekly Alpha subscription. Cached ~10min.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`flows`	No
`total`	No
`summaries`	No
`updatedAt`	No
`dataSource`	No
`attribution`	No
`requiredTierForFull`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "dataSource": {
+      "type": "string"
+    },
+    "flows": {
+      "items": {
+        "properties": {
+          "amountUsd": {
+            "type": "number"
+          },
+          "bridge": {
+            "type": "string"
+          },
+          "destChain": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "explorerUrl": {
+            "format": "uri",
+            "type": "string"
+          },
+          "sourceChain": {
+            "type": "string"
+          },
+          "tokenSymbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "requiredTierForFull": {
+      "type": "string"
+    },
+    "summaries": {
+      "items": {
+        "properties": {
+          "bridge": {
+            "type": "string"
+          },
+          "totalVolume24h": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already mark the call read-only/idempotent/non-destructive. The description adds genuinely useful behavioral details beyond that: free-tier truncation to 'top 3 flows + 2 bridge summaries', auth gating for full history via 'Weekly Alpha subscription', and data staleness via 'Cached ~10min'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but it repeats 'recent large cross-chain bridge transfers' and buries 'top 3 free; capital-rotation signal' in an awkward em-dash aside. It could be tightened to one or two clear sentences without losing meaning.

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?

Given zero parameters, an output schema, and annotations covering the safety profile, the description is mostly complete: it covers source, scope, subscription limits, and cache freshness. It is slightly incomplete in not naming the obvious sibling history tool and not explaining the 'capital-rotation signal' label.

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 has zero properties, so there are no parameters to clarify; this is the baseline-4 case. The 'top 3 free' note refers to output truncation, not an input parameter, so no additional parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete read operation: 'Get recent large cross-chain bridge transfers' and adds 'per-bridge volume summaries sourced from LI.FI.' It is clear in scope (recent, large, top-3 free) and implies it is a snapshot rather than full history, though it never explicitly names the sibling tool bridge_flow_history.

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?

Provides helpful context: 'Free preview: top 3 flows + 2 bridge summaries' and 'Cached ~10min' signal that this is a lightweight, limited snapshot. However, it does not explicitly state when to prefer bridge_flow_history or when this tool is insufficient beyond the subscription mention.

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

All whale-insights 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.

Resources

Need Help?