Skip to main content
Glama
Sign In
Alchemy MCP Server

Alchemy MCP Server

Official
by alchemyplatform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

sendTransaction

Send a transaction from a smart contract account (SCA) to any address using the Alchemy Wallet API. Requires owner SCA address, signer address, and recipient address; optional value and call data.

Instructions

Send a transaction from a smart contract account (SCA) via the Alchemy wallet API. Requires AGENT_WALLET_SERVER

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ownerScaAccountAddress": "<ownerScaAccountAddress>",
      "signerAddress": "<signerAddress>",
      "toAddress": "<toAddress>"
    },
    "name": "sendTransaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerScaAccountAddressYesThe owner SCA account address.
signerAddressYesThe signer address to send the transaction from.
toAddressYesThe address to send the transaction to.
valueNoThe value of the transaction in ETH.
callDataNoThe data of the transaction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'Send a transaction', implying a mutation, but does not disclose side effects, reversibility, fees, authorization scope, or error conditions. The agent lacks behavioral context.

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 short (two sentences) with no redundant information. It is front-loaded with the core action. However, it misses an opportunity to include essential details like output or examples, which could be added without hurting conciseness.

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?

Given the tool's complexity (5 parameters, 3 required, no output schema), the description is insufficient. It does not explain what the tool returns (e.g., transaction hash) or any post-invocation steps. Sibling tools like 'simulateAssetChanges' have more contextual description.

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?

The input schema has 100% description coverage for all 5 parameters, so the schema already documents them well. The description adds no additional semantic meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 clearly states the verb 'Send' and identifies the resource as 'a transaction from a smart contract account (SCA)'. This distinguishes it from most sibling tools, which are read-only or simulation-related. However, it doesn't specify whether the transaction is an ETH transfer or contract interaction, so it could be more specific.

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?

The description mentions a requirement ('Requires AGENT_WALLET_SERVER'), but gives no guidance on when to use this tool versus alternatives like 'swap' or 'simulateExecution'. There are no exclusions or contextual cues to help the agent decide.

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