Skip to main content
Glama

sendTransaction

Send blockchain transactions from a smart contract account using specified signer, recipient, value, and data parameters.

Input Schema

TableJSON 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.

Implementation Reference

  • The core handler function that sends a transaction by posting to the agent wallet server endpoint with the provided parameters.
    async sendTransaction(params: SendTransactionParams) {
      const { ownerScaAccountAddress, signerAddress, toAddress, value, callData } = params;
      try {
        const response = await fetch(`${AGENT_WALLET_SERVER}/transactions/send`, {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
          },
          body: JSON.stringify({
            ownerScaAccountAddress,
            signerAddress,
            toAddress,
            value,
            callData
          })
        });
    
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData.error || `HTTP ${response.status}: ${response.statusText}`);
        }
    
        const result = await response.json();
        return result.data;
      } catch (error) {
        console.error('Error sending transaction:', error);
        throw error;
      }
    },
  • TypeScript interface defining the input parameters for the sendTransaction tool.
    export interface SendTransactionParams {
      ownerScaAccountAddress: string;
      signerAddress: string;
      toAddress: string;
      value?: string;
      callData?: string;
    }
  • index.ts:317-342 (registration)
    Registers the sendTransaction tool with the MCP server, providing Zod input schema validation and a wrapper handler that calls the alchemyApi implementation.
    server.tool('sendTransaction', {
      ownerScaAccountAddress: z.string().describe('The owner SCA account address.'),
      signerAddress: z.string().describe('The signer address to send the transaction from.'),
      toAddress: z.string().describe('The address to send the transaction to.'),
      value: z.string().optional().describe('The value of the transaction in ETH.'),
      callData: z.string().optional().describe('The data of the transaction.'),
      }, async (params) => {
        try {
          const result = await alchemyApi.sendTransaction(params);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
          };
        } catch (error) {
          if (error instanceof Error) {
            console.error('Error in sendTransaction:', error);
            return {
              content: [{ type: "text", text: `Error: ${error.message}` }],
              isError: true
            };
          }
          return {
            content: [{ type: "text", text: 'Unknown error occurred' }],
            isError: true
          };
        }
      })
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/alchemyplatform/alchemy-mcp-server'

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