Skip to main content
Glama
Sign In
Blockchain MCP Server

Blockchain MCP Server

by lienhage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Send Transaction

send-transaction

Execute transactions to smart contracts on EVM-compatible chains by specifying chain, contract address, ABI-encoded data, and private key securely.

Instructions

Send a transaction to a smart contract on any EVM-compatible chain (requires private key)

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": {
      "chain": "<chain>",
      "to": "<to>",
      "data": "<data>",
      "privateKey": "<privateKey>"
    },
    "name": "send-transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain identifier. Available: ethereum, polygon, bsc, arbitrum, optimism, avalanche, fantom, sepolia
dataYesABI-encoded function call data
gasLimitNoGas limit for the transaction
gasPriceNoGas price (in wei)
privateKeyYesPrivate key of the sender (will be handled securely)
toYesContract address to call
valueNoETH value to send (in wei)0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'requires private key' for authentication, but fails to disclose critical traits such as whether the transaction is destructive (likely yes, as it sends), rate limits, error handling, or what happens upon success/failure. This leaves significant gaps for a mutation tool.

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?

The description is a single, efficient sentence that front-loads the core purpose and key constraint ('requires private key'). It contains no wasted words and is appropriately sized for the tool's complexity.

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 (a mutation operation with 7 parameters, no annotations, and no output schema), the description is incomplete. It lacks information on behavioral traits (e.g., destructiveness, response format), error scenarios, and does not compensate for the absence of annotations or output schema, leaving the agent with insufficient context.

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 the schema already documents all 7 parameters thoroughly. The description adds no additional parameter semantics beyond what the schema provides, such as explaining interactions between parameters or usage examples. Baseline 3 is appropriate as 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 clearly states the specific action ('send a transaction'), target ('smart contract'), and scope ('any EVM-compatible chain'), distinguishing it from sibling tools like get-balance or static-call. It directly addresses what the tool does without being tautological.

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

Usage Guidelines3/5

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

The description implies usage by mentioning 'requires private key', which suggests authentication needs, but does not explicitly state when to use this tool versus alternatives like static-call (for read-only calls) or provide context on prerequisites. It offers some guidance but lacks explicit alternatives or exclusions.

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

Related Tools