Skip to main content
Glama

trace crypto funds

trace_crypto_funds
Read-only

Trace where crypto funds went from a wallet address or transaction hash (fund flows, transaction relationships), using 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": "trace_crypto_funds"
  }
}

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

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, so the description's job is to add context – and it does, disclosing data provenance (MistTrack/SlowMist) and the exact return payload (agent description, price, free runs, run link, ready-to-send request). That last item usefully signals this surfaces a request template rather than the trace result itself, though it never explains where that request is sent or whether any auth/payment step follows.

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 verb and resource, with the provider name and return payload following. Efficient, though 'using MistTrack by SlowMist on Finch' is dense with vendor jargon that is not unpacked.

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?

Read-only, open-world, no output schema – the description does explain the return format, which is the main thing missing otherwise. But for a tool whose output is a request to be sent elsewhere, it omits the crucial next step and how the target address should be supplied, so an agent cannot fully act on it without guesswork.

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 optional parameter at 100% schema coverage, the baseline of 3 applies; the description adds no detail about how to phrase the 'task' value. It also implies the wallet address is an input while the schema exposes no address field, leaving the agent to guess that the address belongs inside the free-text task string.

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 ('Trace where crypto funds went') plus the accepted input forms (wallet address or transaction hash) and the underlying provider (MistTrack by SlowMist on Finch). It never names or contrasts with the closest sibling, check_wallet_address_risk, so the agent must infer the fund-flow vs. risk-scoring split.

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: the description tells you the tool takes a wallet address or transaction hash, which suggests the invocation context, but there is no explicit when-to-use/when-not, no prerequisites, and no pointer to check_wallet_address_risk or assess_onchain_business as alternatives.

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.