Skip to main content
Glama
MoralisWeb3

Moralis MCP Server

Official
by MoralisWeb3

evm_getswapsbypairaddress

Retrieve swap transactions for a specific token pair to analyze trading activity, liquidity changes, and transaction history across multiple blockchain networks.

Instructions

Fetch swap transactions (buy, sell, add/remove liquidity) for a specific token pair.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoThe chain to queryeth
addressYesThe pair address token-transactions are to be retrieved for.
cursorNoThe cursor returned in the previous response (used for getting the next page).
limitNoThe desired page size of the result.
fromBlockNoThe minimum block number from which to get the token transactions * Provide the param 'fromBlock' or 'fromDate' * If 'fromDate' and 'fromBlock' are provided, 'fromBlock' will be used.
toBlockNoThe block number to get the token transactions from
fromDateNoThe start date from which to get the token transactions (format in seconds or datestring accepted by momentjs) * Provide the param 'fromBlock' or 'fromDate' * If 'fromDate' and 'fromBlock' are provided, 'fromBlock' will be used.
toDateNoThe end date from which to get the token transactions (format in seconds or datestring accepted by momentjs) * Provide the param 'toBlock' or 'toDate' * If 'toDate' and 'toBlock' are provided, 'toBlock' will be used.
orderNoThe order of the result, in ascending (ASC) or descending (DESC)DESC
transactionTypesNoArray of transaction types. Allowed values are 'buy', 'sell', 'addLiquidity', 'removeLiquidity'.

Implementation Reference

  • Generic handler that implements the core logic for executing the tool by proxying to the Moralis EVM API endpoint corresponding to getSwapsByPairAddress.
    export async function executeApiTool(
      toolName: string,
      definition: McpToolDefinition,
      toolArgs: JsonObject,
      allSecuritySchemes: Record<string, any>,
      token?: string,
    ): Promise<CallToolResult> {
      try {
        // Validate arguments against the input schema
        let validatedArgs: JsonObject;
        try {
          const zodSchema = getZodSchemaFromJsonSchema(
            definition.inputSchema,
            toolName,
          );
          const argsToParse =
            typeof toolArgs === 'object' && toolArgs !== null ? toolArgs : {};
          validatedArgs = zodSchema.parse(argsToParse);
        } catch (error: unknown) {
          if (error instanceof ZodError) {
            const validationErrorMessage = `Invalid arguments for tool '${toolName}': ${error.errors.map((e) => `${e.path.join('.')} (${e.code}): ${e.message}`).join(', ')}`;
            return { content: [{ type: 'text', text: validationErrorMessage }] };
          } else {
            const errorMessage =
              error instanceof Error ? error.message : String(error);
            return {
              content: [
                {
                  type: 'text',
                  text: `Internal error during validation setup: ${errorMessage}`,
                },
              ],
            };
          }
        }
    
        // Prepare URL, query parameters, headers, and request body
        let urlPath = definition.pathTemplate;
        const queryParams: Record<string, any> = {};
        const headers: Record<string, string> = {
          Accept: 'application/json',
          'X-Moralis-Platform': 'MCP',
        };
        let requestBodyData: any = undefined;
    
        // Apply parameters to the URL path, query, or headers
        definition.executionParameters.forEach((param) => {
          const value = validatedArgs[param.name];
          if (typeof value !== 'undefined' && value !== null) {
            if (param.in === 'path') {
              urlPath = urlPath.replace(
                `{${param.name}}`,
                encodeURIComponent(String(value)),
              );
            } else if (param.in === 'query') {
              queryParams[param.name] = value;
            } else if (param.in === 'header') {
              headers[param.name.toLowerCase()] = String(value);
            }
          }
        });
    
        // Ensure all path parameters are resolved
        if (urlPath.includes('{')) {
          throw new Error(`Failed to resolve path parameters: ${urlPath}`);
        }
    
        // Construct the full URL
        const requestUrl = `${definition.baseUrl}${urlPath}`;
    
        // Handle request body if needed
        if (
          definition.requestBodyContentType &&
          typeof validatedArgs['requestBody'] !== 'undefined'
        ) {
          requestBodyData = validatedArgs['requestBody'];
          headers['content-type'] = definition.requestBodyContentType;
        }
    
        // Apply security requirements if available
        // Security requirements use OR between array items and AND within each object
        const appliedSecurity = definition.securityRequirements?.find((req) => {
          // Try each security requirement (combined with OR)
          return Object.entries(req).every(([schemeName, scopesArray]) => {
            const scheme = allSecuritySchemes[schemeName];
            if (!scheme) return false;
    
            // API Key security (header, query, cookie)
            if (scheme.type === 'apiKey') {
              return !!token || !!Config.MORALIS_API_KEY;
            }
    
            return false;
          });
        });
    
        // If we found matching security scheme(s), apply them
        if (appliedSecurity) {
          // Apply each security scheme from this requirement (combined with AND)
          for (const [schemeName, scopesArray] of Object.entries(appliedSecurity)) {
            const scheme = allSecuritySchemes[schemeName];
    
            // API Key security
            if (scheme?.type === 'apiKey') {
              const apiKey = token || Config.MORALIS_API_KEY;
              if (apiKey) {
                if (scheme.in === 'header') {
                  headers[scheme.name.toLowerCase()] = apiKey;
                  console.error(
                    `Applied API key '${schemeName}' in header '${scheme.name}'`,
                  );
                }
              }
            }
          }
        }
        // Log warning if security is required but not available
        else if (definition.securityRequirements?.length > 0) {
          // First generate a more readable representation of the security requirements
          const securityRequirementsString = definition.securityRequirements
            .map((req) => {
              const parts = Object.entries(req)
                .map(([name, scopesArray]) => {
                  const scopes = scopesArray as string[];
                  if (scopes.length === 0) return name;
                  return `${name} (scopes: ${scopes.join(', ')})`;
                })
                .join(' AND ');
              return `[${parts}]`;
            })
            .join(' OR ');
    
          console.warn(
            `Tool '${toolName}' requires security: ${securityRequirementsString}, but no suitable credentials found.`,
          );
        }
    
        // Prepare the axios request configuration
        const config: AxiosRequestConfig = {
          method: definition.method.toUpperCase(),
          url: requestUrl,
          params: queryParams,
          headers: headers,
          ...(requestBodyData !== undefined && { data: requestBodyData }),
        };
    
        // Log request info to stderr (doesn't affect MCP output)
        console.error(
          `Executing tool "${toolName}": ${config.method} ${config.url}`,
        );
    
        // Execute the request
        const response = await axios(config);
    
        // Process and format the response
        let responseText = '';
        const contentType = response.headers['content-type']?.toLowerCase() || '';
    
        // Handle JSON responses
        if (
          contentType.includes('application/json') &&
          typeof response.data === 'object' &&
          response.data !== null
        ) {
          try {
            responseText = JSON.stringify(response.data, null, 2);
          } catch (e) {
            responseText = '[Stringify Error]';
          }
        }
        // Handle string responses
        else if (typeof response.data === 'string') {
          responseText = response.data;
        }
        // Handle other response types
        else if (response.data !== undefined && response.data !== null) {
          responseText = String(response.data);
        }
        // Handle empty responses
        else {
          responseText = `(Status: ${response.status} - No body content)`;
        }
    
        // Return formatted response
        return {
          content: [
            {
              type: 'text',
              text: `API Response (Status: ${response.status}):\n${responseText}`,
            },
          ],
        };
      } catch (error: unknown) {
        // Handle errors during execution
        let errorMessage: string;
    
        // Format Axios errors specially
        if (axios.isAxiosError(error)) {
          errorMessage = formatApiError(error);
        }
        // Handle standard errors
        else if (error instanceof Error) {
          errorMessage = error.message;
        }
        // Handle unexpected error types
        else {
          errorMessage = `Unexpected error: ${String(error)}`;
        }
    
        // Log error to stderr
        console.error(
          `Error during execution of tool '${toolName}':`,
          errorMessage,
        );
    
        // Return error message to client
        return { content: [{ type: 'text', text: errorMessage }] };
      }
    }
  • src/server.ts:96-122 (registration)
    MCP CallTool request handler registration. Retrieves tool definition by name and dispatches to executeApiTool.
    server.setRequestHandler(
      CallToolRequestSchema,
      async (request: CallToolRequest, c): Promise<CallToolResult> => {
        const { name: toolName, arguments: toolArgs } = request.params;
        const toolDefinition = toolDefinitionMap[toolName];
        if (!toolDefinition) {
          console.error(`Error: Unknown tool requested: ${toolName}`);
          return {
            content: [
              {
                type: 'text',
                text: `Error: Unknown tool requested: ${toolName}`,
              },
            ],
          };
        }
        return executeApiTool(
          toolName,
          toolDefinition,
          toolArgs ?? {},
          securitySchemes,
          c.authInfo?.token,
        );
      },
    );
    
    server.setRequestHandler(ListPromptsRequestSchema, async () => {
  • src/server.ts:66-72 (registration)
    Populates the toolDefinitionMap with all extracted tools from EVM and Solana configs, including evm_getswapsbypairaddress.
    let toolDefinitionMap: Record<string, McpToolDefinition> = {};
    for (const config of configArray)
      toolDefinitionMap = {
        ...toolDefinitionMap,
        ...(await mapToolDefinitions(config)),
      };
  • Extracts tool definitions from OpenAPI spec, generating name/inputSchema/etc. for evm_getswapsbypairaddress from the corresponding operation.
    export function extractToolsFromApi(
      api: OpenAPIV3DocumentX,
      prefix?: string
    ): McpToolDefinition[] {
      const tools: McpToolDefinition[] = [];
      const usedNames = new Set<string>();
      const globalSecurity = api.security || [];
    
      if (!api.paths) return tools;
    
      for (const [path, pathItem] of Object.entries(api.paths)) {
        if (!pathItem) continue;
    
        for (const method of Object.values(OpenAPIV3.HttpMethods)) {
          const operation = pathItem[method];
          if (!operation) continue;
    
          // Generate a unique name for the tool
          let baseName = operation.operationId || generateOperationId(method, path);
          if (!baseName) continue;
    
          // Sanitize the name to be MCP-compatible (only a-z, 0-9, _, -)
          baseName = baseName
            .replace(/\./g, '_')
            .replace(/[^a-z0-9_-]/gi, '_')
            .toLowerCase();
    
          let finalToolName = baseName;
          let counter = 1;
          while (usedNames.has(finalToolName)) {
            finalToolName = `${baseName}_${counter++}`;
          }
          usedNames.add(finalToolName);
    
          // Get or create a description
          const description =
            operation.description ||
            operation.summary ||
            `Executes ${method.toUpperCase()} ${path}`;
    
          const prompt = operation['x-mcp-prompt'];
    
          // Generate input schema and extract parameters
          const { inputSchema, parameters, requestBodyContentType } =
            generateInputSchemaAndDetails(operation);
    
          // Extract parameter details for execution
          const executionParameters = parameters.map((p) => ({
            name: p.name,
            in: p.in,
          }));
    
          // Determine security requirements
          const securityRequirements =
            operation.security === null
              ? globalSecurity
              : operation.security || globalSecurity;
    
          // Create the tool definition
          tools.push({
            name: prefix + finalToolName,
            description,
            inputSchema,
            method,
            pathTemplate: path,
            parameters,
            executionParameters,
            requestBodyContentType,
            securityRequirements,
            operationId: baseName,
            prompt,
          });
        }
      }
    
      return tools;
    }
  • EVM API configuration defining the 'evm_' prefix and URLs to the Moralis Deep Index API spec/endpoints.
    evm:  {
      prefix: 'evm_',
      baseUrl:
        process.env.API_BASE_URL || 'https://deep-index.moralis.io/api/v2.2',
      specUrl:
        process.env.API_SPEC_URL ||
        'https://deep-index.moralis.io/api-docs-2.2/v2.2/swagger.json',
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what data is fetched without behavioral details. It doesn't disclose pagination behavior (implied by 'cursor' parameter but not explained), rate limits, authentication requirements, error conditions, or response format. For a read operation with 10 parameters, this is insufficient.

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 without unnecessary words. Every element ('Fetch swap transactions', transaction types, token pair focus) contributes directly to understanding the tool's function.

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?

For a tool with 10 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the response structure, pagination behavior, error handling, or usage constraints. While the schema documents parameters well, the description fails to provide necessary operational context for effective tool invocation.

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 parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying 'address' refers to a token pair. This meets the baseline for high schema coverage but doesn't provide extra value like explaining parameter interactions or constraints.

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 ('Fetch swap transactions') and resource ('for a specific token pair'), specifying the types of transactions included (buy, sell, add/remove liquidity). It distinguishes from some siblings like 'evm_getswapsbytokenaddress' and 'evm_getswapsbywalletaddress' by focusing on token pairs, but doesn't explicitly differentiate from 'evm_getsnipersbypairaddress' or 'solana_getswapsbypairaddress'.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, constraints, or compare it to similar tools like 'evm_getswapsbytokenaddress' or 'evm_getsnipersbypairaddress', leaving the agent without context for tool selection.

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/MoralisWeb3/moralis-mcp-server'

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