Skip to main content
Glama

check wallet address risk

check_wallet_address_risk
Read-only

Check the risk of a crypto wallet address or transaction with MistTrack by SlowMist on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_wallet_address_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already carry readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior: it returns the agent's description, price, free runs, a run link and a ready-to-send request, implying this tool does not execute the check itself. However, it never explains how the wallet address actually reaches the service, and the schema has no address parameter — a meaningful behavioral gap.

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?

Two sentences, front-loaded with the action and resource, with no filler. The return-value list is dense but each item is informative; only the trailing enumeration borders on enumerating plumbing rather than purpose.

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?

With no output schema, the description does explain what comes back, which is a plus. But for a tool that inspects a wallet address, the absence of any address input — and any explanation of how the address is conveyed via the generic 'task' string — leaves the calling contract incomplete.

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?

There is a single optional 'task' parameter with 100% schema description coverage, so the schema already defines its meaning and the description adds nothing. Per the high-coverage baseline, 3 is appropriate; nothing is lost, but no extra meaning is contributed.

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 gives a specific verb and resource: check the risk of a crypto wallet address or transaction, naming the vendor (MistTrack by SlowMist on Finch). It is clearly distinct from most siblings, though the closely related 'trace_crypto_funds' is never mentioned, so the boundary between risk-checking and fund-tracing is left implicit.

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 only implied by the phrase 'check the risk' — an agent can infer this is for risk scoring rather than tracing. There is no explicit when-to-use, when-not-to-use, or routing to 'trace_crypto_funds', which is the nearest alternative in the sibling list.

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.