Skip to main content
Glama
rsksmart

RSK MCP Server - Rootstock Blockchain Tools

Official
by rsksmart

attest-transfer

Create a transfer attestation on Rootstock using RAS. Provide sender, recipient, amount, transaction hash, block number, timestamp, and transfer type.

Instructions

Create a transfer attestation on Rootstock using RAS. Uses default testnet schema UIDs when none is provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesTransfer amount as a string (e.g., '1.5')
reasonNoOptional reason or memo for the transfer
senderYesSender address (0x... format)
testnetYesUse testnet (true) or mainnet (false)
recipientYesRecipient address of the transfer (0x... format)
schemaUIDNoSchema UID to use - uses default RSK transfer schema if not provided
timestampYesUnix timestamp of the transfer
walletDataNoYour previously saved wallet configuration file content (my-wallets.json)
walletNameNoSpecific wallet name to use - uses current wallet if not provided
blockNumberYesBlock number of the transfer
tokenSymbolNoToken symbol (e.g., 'RBTC', 'RIF') - defaults to RBTC for native transfers; required when tokenAddress is provided
tokenAddressNoERC20 token contract address - omit for RBTC transfers
transferTypeYesType of transfer (e.g., 'native', 'erc20', 'payment')
walletPasswordNoPassword to decrypt the wallet - required when using walletData
transactionHashYesTransfer transaction hash (0x... format, 32 bytes)
Behavior2/5

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

No annotations exist, so the description bears full burden. It discloses creation of an attestation but omits side effects, authorization needs, or reversibility. For a creation tool, this is insufficient.

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?

Single sentence, no extraneous words, front-loaded with purpose. Could benefit from slight restructuring (e.g., listing key behaviors) but is efficient.

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?

Despite 100% schema coverage, the description fails to explain the attestation creation flow, wallet integration, or relationship with related tools (e.g., transfer-tokens). Agents need more context to use correctly.

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%; the description adds no new parameter meaning beyond 'uses default testnet schema UIDs' which is already implied in the schemaUID description. Baseline 3 maintained.

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 it creates a transfer attestation on Rootstock using RAS, with a specific verb and resource. It distinguishes from siblings like transfer-tokens (actual transfer) and issue-attestation (general attestation).

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 such as issue-attestation or detect-attestation. No prerequisites or exclusion criteria provided.

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