Skip to main content
Glama
edkdev

DeFi Trading Agent MCP Server

by edkdev

submit_gasless_swap

Execute cryptocurrency swaps without paying gas fees by signing approval and trade messages. This tool processes gasless transactions using pre-approved quote data.

Instructions

Submit a gasless swap by signing approval and trade messages (no gas fees required)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quoteDataYesQuote data from get_gasless_quote
chainIdNoBlockchain ID (optional if included in quoteData)

Implementation Reference

  • agService helper method: HTTP POST to aggregator API /api/swap/gasless/submit with signed swap data, handles response and errors.
    async submitGaslessSwap(swapData) {
      try {
        const response = await fetch(`${this.baseUrl}/api/swap/gasless/submit`, {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json'
          },
          body: JSON.stringify(swapData)
        });
        
        if (!response.ok) {
          throw new Error(`HTTP ${response.status}: ${response.statusText}`);
        }
        
        const data = await response.json();
        
        if (!data.success) {
          throw new Error(data.error || 'Gasless swap submission failed');
        }
        
        return data.data;
      } catch (error) {
        throw new Error(`Failed to submit gasless swap: ${error.message}`);
      }
    }
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 mentions 'signing approval and trade messages' and 'no gas fees required', which hints at a mutation operation with specific authentication needs, but it lacks details on permissions, rate limits, error conditions, or what the tool returns (no output schema). This leaves significant behavioral gaps.

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 action and key benefit ('no gas fees required'). Every word earns its place with no redundancy or unnecessary details.

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 complexity of a swap operation with no annotations and no output schema, the description is incomplete. It doesn't cover return values, error handling, or behavioral nuances like what 'signing' entails or potential side effects, leaving the agent with insufficient context for reliable use.

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 both parameters (quoteData and chainId). The description adds minimal value by referencing get_gasless_quote for quoteData, but doesn't explain parameter interactions or usage beyond what's in the schema. Baseline 3 is appropriate given high schema coverage.

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 action ('submit a gasless swap') and mechanism ('by signing approval and trade messages'), distinguishing it from sibling tools like execute_swap. However, it doesn't specify what resource is being swapped (e.g., tokens), making it slightly less specific than ideal.

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 when gas fees are undesirable and when quote data is available from get_gasless_quote, but it doesn't explicitly state when to use this tool versus alternatives like execute_swap or provide any exclusions or prerequisites beyond the quote data requirement.

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/edkdev/defi-trading-mcp'

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