Agent Einstein — Crypto & Market Intelligence

Smart-Money Net Inflow

get_smart_money_inflow

Read-onlyIdempotent

Tokens ranked by NET smart-money inflow in US dollars over the last 24 hours, from wallets Binance tracks as consistently profitable. Reports the number of distinct wallets behind each figure — a large inflow from one wallet is a position, not a consensus. BSC. Use when asked what smart money is buying or where informed flow is going.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Rows to return (1-15).

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	No	Tokens ranked by smart-money inflow.
`chain`	No	Chain the screen ran on.
`object`	No	Always "smart-money-inflow".
`period`	No	Lookback period.
`reason`	No	Why the payload is absent, when `available` is false.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "chain": {
+      "description": "Chain the screen ran on."
+    },
+    "object": {
+      "description": "Always \"smart-money-inflow\"."
+    },
+    "period": {
+      "description": "Lookback period."
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "rows": {
+      "description": "Tokens ranked by smart-money inflow.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chainId": {
+            "description": "EVM chain id."
+          },
+          "contractAddress": {
+            "description": "Token contract."
+          },
+          "holders": {
+            "description": "Holder count."
+          },
+          "holdersTop10Pct": {
+            "description": "Share held by the top 10 holders — concentration risk."
+          },
+          "inflowUsd": {
+            "description": "Net smart-money inflow — what the ranking is on."
+          },
+          "kycHolders": {
+            "description": "Holders with a KYC attestation."
+          },
+          "launchTime": {
+            "description": "When the token launched."
+          },
+          "liquidityUsd": {
+            "description": "Pool liquidity."
+          },
+          "marketCapUsd": {
+            "description": "Market cap in USD."
+          },
+          "priceChangePct": {
+            "description": "Percentage price change over the period."
+          },
+          "priceUsd": {
+            "description": "Price in USD."
+          },
+          "riskLevel": {
+            "description": "Risk grade."
+          },
+          "symbol": {
+            "description": "Token symbol."
+          },
+          "traders": {
+            "description": "Distinct traders."
+          },
+          "volumeUsd": {
+            "description": "Period volume."
+          }
+        }
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedAug 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable interpretive context: it reports distinct wallet counts and warns that a large single-wallet inflow is 'a position, not a consensus,' plus it specifies the chain (BSC) and timeframe. This goes beyond annotations without contradicting them.

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?

Three sentences with no fluff: the first states what and how, the second adds an important interpretative caveat, and the third gives usage guidance. Each sentence earns its place and the main purpose is front-loaded.

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 a simple one-parameter read-only tool with an output schema present, the description covers the key context: metric, timeframe, data source, chain, interpretation, and when to use. There is no missing information an agent would need to call it 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 only parameter, limit, is fully documented in the schema with description 'Rows to return (1-15).' Schema coverage is 100%, so the description does not need to add parameter details. The description adds no extra meaning beyond the schema, meeting the baseline but not exceeding it.

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?

The description clearly states a specific verb ('ranked'), resource ('tokens'), metric ('NET smart-money inflow in US dollars'), and timeframe ('last 24 hours'). It distinguishes implicitly from the similar sibling get_smart_money_flow by emphasizing 'NET' and 'BSC', but does not explicitly name the sibling or state the exact differentiation.

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?

The description includes an explicit usage trigger: 'Use when asked what smart money is buying or where informed flow is going.' This gives clear context for when the tool applies. It does not mention when-not-to-use or name alternatives, so it falls short of a full 5.

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

All Agent Einstein — Crypto & Market Intelligence 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.