intel

wallet_risk

Read-only

Risk profile of one wallet address across chains: risk score, mixer funding and source, dormancy, transaction count and value, protocols used, bridge count, flagged (true when funded by a mixer or on the OFAC SDN list, with flagReasons), plus its recent bridge, mixer and transfer events. sanctioned: on the OFAC SDN address list. entity: the exchange name when the address is a labelled exchange hot wallet or deposit address. A wallet dropped from the live profile table in the last 30 days is answered from its newest saved profile (fromHistory true, evictedAt); history lists the saved profiles of the last 30 days, newest first, up to 20 per chain. Public onchain behaviour only. Price: 5 cents per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "wallet_risk"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Chain name, one of bitcoin, ethereum, bnb, solana, avalanche, xrp, tron, polygon, sui; absent = every chain. Example: bnb
`address`	Yes	Wallet address: 0x and 40 hex characters on EVM chains, or the chain native form of 25 to 90 letters and digits. Example: 0x000000000000000000000000000000000000dead

Output Schema

Name	Required	Description
`entity`	No
`source`	No
`address`	Yes
`history`	No
`dataGaps`	No	Present only when the window of the answer overlaps a recorded data gap. Figures inside each listed period are incomplete. periods are the recorded gaps (end null while still open); atCall is measured against the window of this call and is left out of meta.contentHash.
`profiled`	Yes
`profiles`	No
`sanctioned`	No
`recentEvents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / address / description

Added value: +"Wallet address: 0x and 40 hex characters on EVM chains, or the chain native form of 25 to 90 letters and digits. Example: 0x000000000000000000000000000000000000dead"

addedInput schema / properties / chain / description

Added value: +"Chain name, one of bitcoin, ethereum, bnb, solana, avalanche, xrp, tron, polygon, sui; absent = every chain. Example: bnb"

Changed1 schema field changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"

Changed2 schema fields changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"

changedInput schema / x-lexicon / version

Previous value: -"0.1.0"New value: +"0.2.0"

Changed7 schema fields changedOct 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / dataGaps

Added value: +{
+  "additionalProperties": false,
+  "description": "Present only when the window of the answer overlaps a recorded data gap. Figures inside each listed period are incomplete. periods are the recorded gaps (end null while still open); atCall is measured against the window of this call and is left out of meta.contentHash.",
+  "properties": {
+    "gaps": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "atCall": {
+            "additionalProperties": false,
+            "properties": {
+              "note": {
+                "type": "string"
+              },
+              "periodsInWindow": {
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "end": {
+                      "type": "number"
+                    },
+                    "ongoing": {
+                      "type": "boolean"
+                    },
+                    "start": {
+                      "type": "number"
+                    }
+                  },
+                  "required": [
+                    "start",
+                    "end"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "shareOfWindowPct": {
+                "type": "number"
+              },
+              "windowEnd": {
+                "type": "number"
+              },
+              "windowStart": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "windowStart",
+              "windowEnd",
+              "periodsInWindow",
+              "shareOfWindowPct",
+              "note"
+            ],
+            "type": "object"
+          },
+          "chain": {
+            "type": "string"
+          },
+          "data": {
+            "type": "string"
+          },
+          "periods": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "end": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "ongoing": {
+                  "type": "boolean"
+                },
+                "start": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "start",
+                "end"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "records": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "lost": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "lostUnit": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "record": {
+                  "type": "string"
+                },
+                "source": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "source",
+                "record"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "section": {
+            "type": "string"
+          },
+          "window": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "section",
+          "chain",
+          "data",
+          "window",
+          "periods",
+          "records",
+          "atCall"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "statement": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "statement",
+    "gaps"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / entity

Added value: +{
+  "additionalProperties": true,
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / history

Added value: +{
+  "type": [
+    "array",
+    "null"
+  ]
+}

removedOutput schema / properties / meta

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "contentHash": {
-      "type": "string"
-    },
-    "generated": {
-      "type": "number"
-    },
-    "priceUsd": {
-      "type": "number"
-    },
-    "validUntil": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / receipt

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "bytes": {
-      "type": "number"
-    },
-    "covers": {
-      "type": "string"
-    },
-    "issuedAt": {
-      "type": "number"
-    },
-    "lookup": {
-      "type": "string"
-    },
-    "network": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "nonce": {
-      "type": "string"
-    },
-    "seq": {
-      "type": "number"
-    },
-    "settleTx": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sha256": {
-      "type": "string"
-    },
-    "tool": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / sanctioned
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "address": [
+    "Address"
+  ]
+}

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab

Added value: +{
+  "address": "onchain.addressApi",
+  "chain": "onchain.chain"
+}

Changed1 schema field changedSep 7, 2026
- addedOutput schema / properties / source
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "contentHash": {
+      "type": "string"
+    },
+    "generated": {
+      "type": "number"
+    },
+    "priceUsd": {
+      "type": "number"
+    },
+    "validUntil": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bytes": {
+      "type": "number"
+    },
+    "covers": {
+      "type": "string"
+    },
+    "issuedAt": {
+      "type": "number"
+    },
+    "lookup": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "seq": {
+      "type": "number"
+    },
+    "settleTx": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sha256": {
+      "type": "string"
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedAug 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With readOnlyHint already declaring a safe read, the description still adds substantive context: the data scope ('Public onchain behaviour only'), a per-call price, the historical fallback rule (fromHistory/evictedAt) and the 20-per-chain history cap. It does not cover rate limits or latency, but the behavioral picture is well beyond what the annotation provides.

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?

It is a single dense paragraph, but front-loaded correctly: the payload comes first, then semantics of flagged/sanctioned/entity, then the history fallback and pricing. The field enumeration is long yet each item is a real return field an agent needs; no filler sentences.

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?

For a multi-chain, moderately complex read tool with an output schema, the description covers data scope, eviction/history behavior, flag semantics and cost. The return-field enumeration partly duplicates the output schema, and it omits any mention of latency or failure modes, so it falls just short of complete.

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?

Schema coverage is 100% and both parameters are documented with enum values and address formats, so the schema carries the load. The description only indirectly touches parameters via 'across chains' and 'up to 20 per chain'; it adds no format or default guidance beyond the schema, which is the expected baseline.

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 opens with a specific verb+resource ('Risk profile of one wallet address across chains') and then enumerates exactly what is returned (risk score, mixer funding, dormancy, tx count/value, protocols, bridge count, flag reasons). It is unmistakable what the tool does, though it never names a sibling (e.g. screened_payer, mev_pool_check, whale_flows) to differentiate scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than directed: the agent learns it should be used for per-address due diligence and that evicted wallets are still served, but there are no explicit when-to-use vs when-not conditions and no alternative tool is referenced. The cost note (5 cents/call) is the only real decision-support signal.

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

All intel 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?