Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-bitcoinAddress

Generate random Bitcoin addresses for mainnet or testnet, with selectable legacy, segwit, bech32, or taproot formats for testing and development.

Instructions

Generates a random Bitcoin address.

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": "finance-bitcoinAddress"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoThe bitcoin address type.
networkNoThe bitcoin network.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations present, the description carries the full disclosure burden and falls short: it says nothing about defaults (e.g., which network/type is used when the optional parameters are omitted), whether output is purely local/offline, or whether generated addresses are cryptographically valid or merely format-shaped.

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?

A single front-loaded sentence with zero filler and no hedging. It is efficient, though the brevity contributes to the missing behavioral detail rather than balancing it.

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?

For a two-optional-parameter generator with no output schema, the description should at minimum state the default behavior when type/network are omitted. Otherwise the definition is minimally viable — enough to call the tool, not enough to predict its output.

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% with both parameters enumerated and described, so the schema already explains the address type and network options. The description adds nothing beyond the schema, which is the baseline expectation at full coverage.

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 states a specific verb ("Generates") and resource ("a random Bitcoin address"), and the "Bitcoin" qualifier separates it from the ethereum/litecoin siblings. It does not explicitly name an alternative, but the domain-specific noun does the disambiguation work.

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?

There is no guidance on when to use this versus the ethereum/litecoin address generators, and no mention of test scenarios or prerequisites. The agent must infer everything from the name and schema.

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