Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Wallet risk score (a heuristic)

get_wallet_risk
Read-onlyIdempotent

A transparent 0-100 risk score for a wallet with named reasons and the evidence behind each: issuer block-list membership, tokens the wallet minted that are now rated danger, flagged tokens it bought (tokens merely sent to it never count), round trips with itself, bot-like trading, a very new wallet. notChecked lists what was not scored (mixers and sanctions lists, scam-labelled counterparties). It is a heuristic, not an accusation: quote disclaimer with the score and never present it as proof of wrongdoing. Wallets without a stake key get no score.

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

Input Schema

NameRequiredDescriptionDefault
addressYesaddr1…, stake1… or $handle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations' read-only/idempotent profile: discloses that it is a heuristic, that `notChecked` enumerates unscored areas (mixers, sanctions lists, scam counterparties), that merely-received tokens are excluded, and that stake-key-less wallets get no score. These are exactly the caveats an agent needs before relaying results.

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?

Front-loads the core definition and packs the signal list into one dense sentence with no filler. The final stake-key caveat is slightly buried at the end but is material, so it earns its place.

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?

Despite having no output schema, the description explains the returned structure — score, named reasons, evidence per reason, `notChecked`, and `disclaimer`. An agent could relay results correctly with nothing missing.

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?

Schema coverage is 100% and the single parameter is documented, so baseline is 3; the description adds value by noting that only stake-key-bearing wallets are scored even though handles and addr1 forms are accepted. It doesn't restate the address pattern, which is correct.

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+resource with scope: a transparent 0-100 risk score for a wallet, plus the exact signals it draws on (issuer block-list, minted danger tokens, bought flagged tokens, round trips, bot-like trading, wallet age). This is clearly distinct from siblings like get_token_safety (token-level) and get_wallet (identity/lookup).

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 real usage constraints: never present the score as proof of wrongdoing and always quote the disclaimer; wallets without a stake key return no score. What's missing is explicit routing to alternatives (e.g. token-level risk via get_token_safety), so it's clear context but not full when/when-not guidance.

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

All Realtap toolsInspect
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