Skip to main content
Glama
laszlopere

mcp-bytesmith

bip39

Generate new or validate existing BIP-39 mnemonics, and convert them to 64-byte seeds for BIP-32 key derivation.

Instructions

Generate, validate, or convert a BIP-39 mnemonic to a seed.

action=generate -> {action, mnemonic, word_count, strength}. With entropy the mnemonic is deterministic; without it, fresh CSPRNG entropy of strength bits. action=validate -> {action, valid, word_count} plus a reason when invalid — a bad mnemonic is a soft result, not an error (§2.0.5). action=to_seed -> {action, seed, word_count}: the 64-byte seed as 0x-hex, ready for bip32_derive. PBKDF2-HMAC-SHA512(mnemonic, "mnemonic"+passphrase, 2048). An invalid mnemonic raises here; use action=validate to inspect it first.

Neither the mnemonic, the entropy, nor the passphrase is ever echoed back.

Example: bip39("to_seed", mnemonic="abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about") -> seed="0x5eb00bbd..."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes'generate' builds a mnemonic (from `entropy`, or fresh CSPRNG entropy of `strength` bits); 'validate' checks a mnemonic's wordlist membership and checksum; 'to_seed' derives the 64-byte BIP-32 seed from a mnemonic and optional `passphrase`.
entropyNoEntropy as hex (0x optional) for action=generate: 16, 20, 24, 28, or 32 bytes, giving 12..24 words. Omit to draw fresh CSPRNG entropy of `strength` bits. Never echoed back.
mnemonicNoThe mnemonic sentence (required for validate/to_seed). Casing and extra whitespace are forgiven; it is never echoed back.
strengthNoEntropy bits for action=generate when `entropy` is omitted (128 -> 12 words, 256 -> 24 words). Ignored when `entropy` is given.
passphraseNoThe optional BIP-39 passphrase (the "25th word") for action=to_seed. Any passphrase is valid and yields a DIFFERENT seed, so a wrong one silently opens a different wallet. Never echoed back.
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it explains that invalid mnemonics in to_seed raise errors while validate returns a reason, describes the PBKDF2 derivation, and states that sensitive inputs are never echoed back.

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?

The description is well-structured with bullet points for each action and includes a concrete example. It is slightly verbose with repeated phrases like 'never echoed back,' but overall efficient.

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

Completeness5/5

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

Given the complexity of 5 parameters and no output schema, the description fully explains return value structure for each action, error handling, and format details (e.g., seed as 0x-hex). It leaves no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers all parameters with 100% descriptions. The description adds value by explaining determinism with entropy for generate and the security implication of the passphrase (wrong passphrase yields a different seed).

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 clearly states that the tool generates, validates, or converts BIP-39 mnemonics to seeds, with each action's specific output. This distinguishes it from sibling tools like bip32_derive, which operates on seeds rather than mnemonics.

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

Usage Guidelines4/5

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

The description provides explicit guidance for when to use each action (generate, validate, to_seed) and warns about error behavior for invalid mnemonics. However, it does not explicitly contrast with alternative tools, though the sibling context makes the purpose clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laszlopere/mcp-bytesmith'

If you have feedback or need assistance with the MCP directory API, please join our Discord server