whale-insights

bridge_flow_history

Read-onlyIdempotent

Get daily cross-chain bridge flow history — total volume USD, transaction count, protocol count, and top protocol over up to 90 days — Daily historical cross-chain bridge activity aggregated from LI.FI API (covering 9+ protocols). One row per day: total bridged volume in USD, transaction count, number of active protocols, and the dominant protocol by volume. Useful for tracking cross-chain capital flow trends. DB-backed, 5-min cache. Powered by bridge_flow_daily table (365d retention, permanent monthly archive). — Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of days of history to return (1–90, default 30).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`total`	No
`history`	No
`updatedAt`	No
`attribution`	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"
+    },
+    "days": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "properties": {
+          "date": {
+            "description": "YYYY-MM-DD snapshot date.",
+            "format": "date",
+            "type": "string"
+          },
+          "protocolCount": {
+            "description": "Number of distinct bridge protocols active.",
+            "type": "integer"
+          },
+          "topProtocol": {
+            "description": "Protocol with the highest volume (e.g. 'Stargate', 'Hop').",
+            "nullable": true,
+            "type": "string"
+          },
+          "totalTxCount": {
+            "description": "Total number of bridge transactions.",
+            "type": "integer"
+          },
+          "totalVolumeUsd": {
+            "description": "Total bridged volume in USD across all protocols.",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structure. The description adds meaningful behavioral context beyond annotations: DB-backed with a 5-minute cache, 365-day retention with permanent monthly archive, and aggregation from LI.FI API. These details inform expectations about freshness and data availability without contradicting any annotation.

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 longer than strictly necessary but front-loads the core purpose and outputs before implementation details. The main redundancy is repeating the output fields in both the opening sentence and the 'One row per day' clause. However, every sentence contributes useful context, and the usage guidance is clearly positioned at the end.

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?

This is a simple single-parameter read tool, and the description covers the output row shape, data source, caching, retention, and when to choose an alternative. An output schema exists, so return-value details are already structured. Nothing essential is missing for an agent to select and invoke the tool correctly.

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 single 'days' parameter is fully documented in the schema (1–90, default 30), so schema coverage is 100%. The description adds only marginal semantic value by saying 'over up to 90 days', which largely repeats the schema. This meets the baseline but does not elevate beyond it.

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 opens with a specific verb and resource: 'Get daily cross-chain bridge flow history', then enumerates exact output fields (volume USD, transaction count, protocol count, top protocol) and the data source. It clearly distinguishes this as the daily historical variant, implicitly separating it from the sibling 'bridge_flows' live snapshot tool.

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 description explicitly states when to use this tool: 'Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.' This directly routes an agent between alternatives and provides clear selection criteria.

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?