Skip to main content
Glama

DEX Changes

dex_changes

Retrieve recent changes to DEX trade data filtered by timestamp to monitor on-chain trading activity updates.

Instructions

Get recent changes to DEX trade data since a given timestamp. Cost: $0.003 per query. Source: On-chain DEX analytics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceYesISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)
limitNoMaximum results (default 50)

Implementation Reference

  • The async handler function that executes the dex_changes tool logic. It calls the API endpoint /api/v1/dex/changes with 'since' and 'limit' parameters, handles errors, and returns the change feed results.
    async ({ since, limit }) => {
      const res = await apiGet<DexQueryResponse>("/api/v1/dex/changes", {
        since,
        limit: limit ?? 50,
      });
    
      if (!res.ok) {
        return {
          content: [
            {
              type: "text" as const,
              text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
            },
          ],
          isError: true,
        };
      }
    
      const { count, data } = res.data;
      const warn = stalenessWarning(res);
      const summary = `${warn}Found ${count} DEX change(s) since ${since}.`;
      const json = JSON.stringify(data, null, 2);
    
      return {
        content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
      };
    },
  • Input schema for dex_changes defined with Zod: 'since' (required ISO 8601 string) and 'limit' (optional int 1-100, default 50).
    inputSchema: {
      since: z
        .string()
        .describe("ISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)"),
      limit: z
        .number()
        .int()
        .min(1)
        .max(100)
        .optional()
        .describe("Maximum results (default 50)"),
    },
  • Registration of the tool named 'dex_changes' via server.registerTool(), including metadata (title, description, cost info) and the input schema.
    server.registerTool(
      "dex_changes",
      {
        title: "DEX Changes",
        description:
          "Get recent changes to DEX trade data since a given timestamp. " +
          "Cost: $0.003 per query. Source: On-chain DEX analytics.",
        inputSchema: {
          since: z
            .string()
            .describe("ISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)"),
          limit: z
            .number()
            .int()
            .min(1)
            .max(100)
            .optional()
            .describe("Maximum results (default 50)"),
        },
      },
      async ({ since, limit }) => {
        const res = await apiGet<DexQueryResponse>("/api/v1/dex/changes", {
          since,
          limit: limit ?? 50,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const warn = stalenessWarning(res);
        const summary = `${warn}Found ${count} DEX change(s) since ${since}.`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • src/index.ts:33-61 (registration)
    The parent registration: registerDexTools(server) is called at line 52, which registers the dex_changes tool among other DEX tools.
    function createMcpServer() {
      const server = new McpServer({
        name: "verilex-data",
        version: "0.3.3",
      });
    
      registerNpiTools(server);
      registerSecTools(server);
      registerPacerTools(server);
      registerWeatherTools(server);
      registerOtcTools(server);
      registerTrademarkTools(server);
      registerPatentTools(server);
      registerCompanyTools(server);
      registerCryptoTools(server);
      registerSanctionsTools(server);
      registerWhaleTools(server);
      registerLabelTools(server);
      registerHolderTools(server);
      registerDexTools(server);
      registerContractTools(server);
      registerPmTools(server);
      registerPmArbTools(server);
      registerPmResolutionTools(server);
      registerEconTools(server);
      registerPmMicroTools(server);
    
      return server;
    }
  • The apiGet helper used by the dex_changes handler to make the GET request to the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
      const url = buildUrl(path, params);
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "verilex-mcp-server/0.1.0",
      };
    
      // Forward x402 payment token if present in env (for paid endpoints)
      const paymentToken = process.env.VERILEX_PAYMENT_TOKEN;
      if (paymentToken) {
        headers["X-Payment-Token"] = paymentToken;
      }
    
      const res = await fetch(url, { headers });
      const data = (await res.json()) as T;
    
      const stale = res.headers.get("X-Data-Stale");
      const lastUpdated = res.headers.get("X-Data-Last-Updated");
      const ageSeconds = res.headers.get("X-Data-Age-Seconds");
    
      return {
        ok: res.ok,
        status: res.status,
        data,
        stale: stale === "true",
        lastUpdated: lastUpdated ?? undefined,
        ageSeconds: ageSeconds ? Number(ageSeconds) : undefined,
      };
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. It discloses cost and source but does not explain what 'changes' exactly means (e.g., whether it's incremental additions or full diffs) or any rate limits. More behavioral context is needed.

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 two sentences with no wasted words. The purpose is front-loaded, and additional info (cost, source) is compactly provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with two parameters and no output schema, the description covers purpose, cost, and source but does not explain what the output looks like or how 'changes' are represented. It is adequate but leaves some gaps.

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 coverage is 100% and both parameters have clear descriptions in the schema (ISO 8601 for 'since', min/max for 'limit'). The description adds no additional parameter information beyond the schema, so baseline score of 3 applies.

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 'Get recent changes to DEX trade data since a given timestamp' with a specific verb and resource. It distinguishes itself from sibling tools like dex_stats or query_dex_trades by focusing on 'changes' but does not explicitly differentiate.

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 only mentions cost per query, which is a usage hint but does not specify when to use this tool versus alternatives or any when-not-to-use criteria.

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/carrierone/verilexdata-mcp'

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