Skip to main content
Glama

search_leaks_by_wallet

Search Vysion's leak database for a cryptocurrency wallet address. Supported chains: BTC, ETH, XMR, XRP, ZEC, DOT, BNB, DASH.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "chain": "<chain>",
      "address": "<address>"
    },
    "name": "search_leaks_by_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
gteNoDate in ISO 8601 format (e.g., '2024-01-01T00:00:00Z' or 'YYYY-MM-DD')
lteNoDate in ISO 8601 format (e.g., '2024-01-01T00:00:00Z' or 'YYYY-MM-DD')
pageNoPage number
chainYesBlockchain (BTC, ETH, XMR, XRP, ZEC, DOT, BNB, DASH)
addressYesWallet address to search for
page_sizeNoResults per page (default 5, max 100). Keep low to avoid large responses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It conveys that this is a read of a leak database and enumerates chain support, but says nothing about authentication, rate limits, whether results are paginated in practice, or what a leak record contains; the trailing "200: Successful Response" boilerplate is an OpenAPI artifact rather than useful disclosure.

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 substantive content is a single front-loaded sentence plus a compact chain list, which is efficient. The appended "### Responses / 200: Successful Response" block is boilerplate noise that adds nothing an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six parameters, fully documented in the schema, and no output schema, so the schema covers argument semantics well. However, for an unannotated search tool the description never characterizes the returned leak records or paging behavior, leaving the agent to infer what a hit looks like.

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 description coverage is 100%, so the schema already documents gte/lte date bounds, page, page_size defaults and the chain/address fields. The description's chain enumeration duplicates the schema's own chain description and adds no new meaning such as address format expectations per chain (e.g., bech32 vs hex).

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?

States a specific verb and resource: "Search Vysion's leak database for a cryptocurrency wallet address," which an agent can distinguish from email/hash/IP searches without opening the schema. It stops short of explicitly naming or contrasting any sibling tool, so differentiation is inferred from the entity type rather than stated.

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?

The supported-chain list (BTC, ETH, XMR, XRP, ZEC, DOT, BNB, DASH) implicitly defines when this tool applies: only these chains are searchable. There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance despite many near-neighbor search tools in the catalog.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources