Skip to main content
Glama
hifriendbot

AgentWallet MCP Server

by hifriendbot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_transaction

Sign and broadcast a transaction. Returns the transaction hash (EVM) or signature (Solana) on success. The transaction is signed server-side and broadcast via RPC.

Instructions

Sign and broadcast a transaction. Returns the transaction hash (EVM) or signature (Solana) on success. The transaction is signed server-side and broadcast via RPC.

Input Schema

NameRequiredDescriptionDefault
toYesDestination address (0x-prefixed for EVM, Base58 for Solana)
dataNoHex-encoded calldata (0x-prefixed) for EVM contract calls
valueNoValue in wei/lamports (decimal integer string; no hex, no decimals)0
max_feeNoMax fee per gas in wei — EVM only (auto if omitted)
chain_idNoChain ID (defaults to wallet's default)
gas_limitNoGas limit — EVM only (auto-estimated if omitted)
wallet_idYesWallet ID
token_mintNoSPL token mint address — Solana only (for SPL token transfers)
priority_feeNoMax priority fee per gas in wei — EVM only (auto if omitted)
token_decimalsNoSPL token decimals, Solana only (6 for USDC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.14.2
    • addedInput schema / properties / data / pattern
      Added value: +"^(0x([0-9a-fA-F]{2})*)?$"
    • addedInput schema / properties / to / pattern
      Added value: +"^(0x[a-fA-F0-9]{40}|[1-9A-HJ-NP-Za-km-z]{32,44})$"
    • changedInput schema / properties / token_decimals / description
      Previous value: -"SPL token decimals — Solana only (6 for USDC)"New value: +"SPL token decimals, Solana only (6 for USDC)"
    • addedInput schema / properties / token_decimals / maximum
      Added value: +36
    • addedInput schema / properties / token_decimals / minimum
      Added value: +0
    • changedInput schema / properties / value / description
      Previous value: -"Value in wei/lamports (decimal string)"New value: +"Value in wei/lamports (decimal integer string; no hex, no decimals)"
    • addedInput schema / properties / value / pattern
      Added value: +"^\\d+$"
  2. First observedv1.7.3

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose key traits: server-side signing (no private key required from the caller), broadcast via RPC, and the cross-chain return format. However, it omits irreversibility, permission or wallet-state prerequisites, and failure behavior, leaving meaningful gaps for a mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and followed by the return format and signing model. Every sentence adds distinct information with no filler or repetition.

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

Completeness4/5

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

Given 10 parameters with 100% schema coverage, no annotations, and no output schema, the description is fairly complete: it explains the server-side signing/broadcast model and the chain-specific return value. It could do slightly more on prerequisites or error conditions, but the schema already covers all inputs.

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%, so every one of the 10 parameters is already documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, which is the expected baseline when the 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 states a specific verb and resource: 'Sign and broadcast a transaction.' The inclusion of 'broadcast' distinguishes it from the sibling sign_transaction, which presumably only signs, so an agent can tell them apart without opening schemas.

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 explicit guidance is given on when to use this tool versus alternatives such as sign_transaction, simulate_transaction, or call_contract. The description implies it is for submitting transactions, but it does not state conditions, prerequisites, or when-not-to-use cases.

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