RelayShield Scam Checks

Check a crypto wallet for risk

check_wallet

Read-only

Returns a read-only risk assessment of a cryptocurrency wallet address. It never moves funds or initiates transactions. Provide address; the chain (EVM, Solana, TON, or Bitcoin) is detected from the address format automatically. Returns a risk level of CRITICAL, HIGH, MEDIUM, LOW, or unknown, with the specific sanctions, scam, drainer, and phishing flags behind it. A verdict of unknown means nothing is known against the address; it does not mean the address is safe.

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": "check_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Wallet address to screen. Chain is auto-detected.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 11, 2026

addedInput schema / properties / address / title
```
Added value: +"Address"
```
addedInput schema / title
```
Added value: +"check_walletArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "check_walletOutput",
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly, non-destructive, open-world) by confirming it never moves funds or initiates transactions, enumerating the risk-level taxonomy, and naming the underlying flag categories (sanctions, scam, drainer, phishing). The caveat that "unknown" means no data rather than safety is a genuinely non-obvious behavioral disclosure that prevents a dangerous misread.

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?

Four short sentences, each carrying distinct load: purpose, safety boundary, chain detection, and output semantics. The most consequential warning (unknown ≠ safe) is placed last for emphasis and nothing is redundant.

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 single-parameter read tool with an output schema, this covers everything an agent needs: what it accepts, how the chain is resolved, what the verdict categories are, and how to interpret the negative-result case. No gaps remain that would cause a misfire.

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?

With one parameter and 100% schema description coverage, the schema already documents `address` and auto-detection. The description restates the same fact rather than adding format examples or constraints, so it meets the baseline without exceeding 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?

States a specific verb and resource up front: "Returns a read-only risk assessment of a cryptocurrency wallet address." The resource (wallet address) is distinct from every sibling (breach, email, link), so an agent can select it without opening the schema.

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?

Gives clear context for use: supply an address and the chain is auto-detected, so no chain parameter or routing decision is needed. It does not explicitly state when to prefer a sibling or what to do for non-address inputs, but the domain is narrow enough that the context is unambiguous.

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

All RelayShield Scam Checks 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?