Skip to main content
Glama
rsksmart

RSK MCP Server - Rootstock Blockchain Tools

Official
by rsksmart

create-wallet

Create, import, or manage Rootstock blockchain wallets. Supports listing, switching, updating names, and deleting wallets with step-by-step guidance.

Instructions

Create a new wallet based on the selected option. This function will ask for required information step by step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
privateKeyNoPrivate key to import - required for 'Import existing wallet' option
walletDataNoYour previously saved wallet configuration file content (my-wallets.json) - required for most operations
walletNameNoThe name for the new wallet - required for create/import operations
passwordFileNoJSON file content with password field - format: {"password": "yourpassword"}
walletOptionYesThe wallet creation option selected by the user
newMainWalletNoName of wallet to switch to - required for 'Switch wallet' option
newWalletNameNoNew name for the wallet - required for 'Update wallet name' option
previousWalletNoCurrent name of wallet to rename - required for 'Update wallet name' option
walletPasswordNoThe password for the wallet - required for create/import operations
deleteWalletNameNoName of wallet to delete - required for 'Delete wallet' option
replaceCurrentWalletNoWhether to replace current wallet - for create/import operations
Behavior2/5

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

The description claims interactive step-by-step questioning, but does not disclose side effects (wallet creation, modification, deletion), required auth, or error states. Without annotations, this is a significant gap.

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 short sentences, no fluff. The phrase 'based on the selected option' is slightly redundant with the parameter, but overall efficient.

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

Completeness1/5

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

Highly incomplete for a complex, multi-mode tool with 11 parameters and no output schema. Does not describe return behavior, error handling, or workflow steps per wallet option.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds 'step by step' interaction hint but does not explain parameter relationships or conditional requirements 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 'Create a new wallet' but the walletOption enum includes 6 different operations (create, import, list, switch, update, delete). The tool is actually a wallet management tool, not just creation. Better purpose clarity would specify 'Manage wallets' or list the supported operations.

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 like 'use-wallet-from-creation' or 'start-wallet-interaction'. The description does not mention prerequisites, typical scenarios, or exclusions.

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/rsksmart/rsk-mcp-server'

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