Crypto MCP Server

get_btc_transactions

Retrieve the most recent Bitcoin transactions for any wallet address. Specify an address and optionally limit the number of transactions returned.

Instructions

Get recent Bitcoin transactions for an address

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_btc_transactions"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of transactions to return (default: 10)
`address`	Yes	Bitcoin wallet address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description must disclose behaviors. It only says 'Get recent transactions' but doesn't clarify whether it returns confirmed/pending transactions, pagination, rate limits, or meaning of 'recent'. Key behavioral gaps for a blockchain tool.

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?

One sentence, 6 words, no fluff. However, it omits important details, so it's not maximally effective. Still, it's concise and front-loaded.

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?

Low complexity but description is minimal: no mention of returned fields, ordering, date range, or error handling. Without output schema, more context is needed for correct use by an AI agent.

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 coverage is 100% (both params described in schema). The description adds no additional meaning beyond the schema; it only repeats the resource. Baseline 3 is appropriate as schema does the heavy lifting.

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?

The description 'Get recent Bitcoin transactions for an address' is specific: verb 'Get', resource 'Bitcoin transactions', and scope 'for an address'. It clearly distinguishes from sibling tools like get_btc_balance (balance) and get_eth_transactions (different blockchain).

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 on when to use this tool versus alternatives, no prerequisites or exclusions. The description simply states what it does without context for selection.

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

Deploy Server