Skip to main content
Glama
Sign In
Bitcoin Data MCP Server

Bitcoin Data MCP Server

by myownipgit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

detect_transaction_patterns

Analyze a Bitcoin transaction to detect common patterns like spending, consolidating, or mixing.

Instructions

Detect patterns in a transaction (basic analysis)

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": {
      "txid": "<txid>"
    },
    "name": "detect_transaction_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
txidYesTransaction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior1/5

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

With no annotations, the description must disclose behavior. It only says 'basic analysis', leaving the agent unaware of side effects, permissions, or read-only nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is too minimal (one sentence, 7 words) and lacks structure. While concise, it sacrifices necessary detail.

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

Completeness2/5

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

For a simple tool with one parameter and no output schema, the description should at least hint at what patterns are detected. It provides insufficient context for correct usage.

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% (txid described as 'Transaction ID'), so the baseline is 3. The description does not add additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Detect patterns in a transaction (basic analysis)', which gives a verb and resource, but it is vague about what patterns are detected and does not distinguish it from sibling tools like analyze_fee_landscape or trace_coin_lineage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites or exclusions.

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

Deploy Server

Other Tools