Skip to main content
Glama
hectortemich

@deonpay/mcp-server

by hectortemich

List transactions

deonpay_list_transactions

Filter and retrieve merchant transactions by status, amount, date, card brand, customer email, and more. Returns paginated results with customer and payment details.

Instructions

List transactions for the merchant with rich filtering. Use this for queries like 'how many sales today', 'show failed transactions this week', 'find payments from cliente@x.com', or 'transactions over $1000 MXN with Visa cards'. Filters include status, source_type (link/checkout), customer_email (partial match), merchant_reference (exact), card_brand (visa/mastercard/amex), date_from/to (ISO), and amount_min/max (centavos). Returns paginated results with customer, card, amount, payment_link summary and timestamps. Amounts in centavos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based). Defaults to 1.
limitNoPage size. Maximum 100, default 20.
statusNo
source_typeNoOrigin of the transaction.
payment_link_idNo
checkout_session_idNo
customer_emailNoPartial match on customer email.
merchant_referenceNoExact merchant_reference filter.
card_brandNo
date_fromNoISO 8601 date or datetime string, e.g. 2026-05-15 or 2026-05-15T10:00:00Z.
date_toNoISO 8601 date or datetime string, e.g. 2026-05-15 or 2026-05-15T10:00:00Z.
amount_minNoMinimum amount in centavos.
amount_maxNoMaximum amount in centavos.

Implementation Reference

  • The handler function for deonpay_list_transactions. It calls client.get('/transactions', compact(args)) where compact() strips undefined/null/empty values from args before passing them as query parameters. Wrapped in safeHandler which catches errors and returns MCP-formatted results.
    safeHandler(async (args) => {
      return client.get("/transactions", compact(args));
    }),
  • Input schema for deonpay_list_transactions with Zod validators. Includes pagination (PageSchema, LimitSchema), filtering by status, source_type, payment_link_id, checkout_session_id, customer_email, merchant_reference, card_brand, date range (IsoDateStringSchema), and amount range in centavos.
    inputSchema: {
      page: PageSchema.optional(),
      limit: LimitSchema.optional(),
      status: TransactionStatusSchema.optional(),
      source_type: z
        .enum(["link", "checkout", "subscription_auto", "subscription_manual"])
        .optional()
        .describe("Origin of the transaction."),
      payment_link_id: z.string().uuid().optional(),
      checkout_session_id: z.string().uuid().optional(),
      customer_email: z.string().optional().describe("Partial match on customer email."),
      merchant_reference: z.string().optional().describe("Exact merchant_reference filter."),
      card_brand: z.enum(["visa", "mastercard", "amex"]).optional(),
      date_from: IsoDateStringSchema.optional(),
      date_to: IsoDateStringSchema.optional(),
      amount_min: z.number().int().min(0).optional().describe("Minimum amount in centavos."),
      amount_max: z.number().int().min(0).optional().describe("Maximum amount in centavos."),
    },
  • Zod enum schema for transaction status values used in the input filter for deonpay_list_transactions.
    const TransactionStatusSchema = z.enum([
      "pending",
      "processing",
      "completed",
      "failed",
      "refunded",
      "partially_refunded",
      "chargeback",
    ]);
  • Registration of the tool on the McpServer via server.registerTool() with name, metadata, and handler. Called from registerTransactionTools() which is invoked by registerAllTools() in index.ts.
    server.registerTool(
      "deonpay_list_transactions",
      {
        title: "List transactions",
        description:
          "List transactions for the merchant with rich filtering. Use this for queries like 'how many sales today', 'show failed transactions this week', 'find payments from cliente@x.com', or 'transactions over $1000 MXN with Visa cards'. Filters include status, source_type (link/checkout), customer_email (partial match), merchant_reference (exact), card_brand (visa/mastercard/amex), date_from/to (ISO), and amount_min/max (centavos). Returns paginated results with customer, card, amount, payment_link summary and timestamps. Amounts in centavos.",
        inputSchema: {
          page: PageSchema.optional(),
          limit: LimitSchema.optional(),
          status: TransactionStatusSchema.optional(),
          source_type: z
            .enum(["link", "checkout", "subscription_auto", "subscription_manual"])
            .optional()
            .describe("Origin of the transaction."),
          payment_link_id: z.string().uuid().optional(),
          checkout_session_id: z.string().uuid().optional(),
          customer_email: z.string().optional().describe("Partial match on customer email."),
          merchant_reference: z.string().optional().describe("Exact merchant_reference filter."),
          card_brand: z.enum(["visa", "mastercard", "amex"]).optional(),
          date_from: IsoDateStringSchema.optional(),
          date_to: IsoDateStringSchema.optional(),
          amount_min: z.number().int().min(0).optional().describe("Minimum amount in centavos."),
          amount_max: z.number().int().min(0).optional().describe("Maximum amount in centavos."),
        },
      },
      safeHandler(async (args) => {
        return client.get("/transactions", compact(args));
      }),
    );
  • The compact() helper used by the handler to strip undefined/null/empty-string entries from the args before sending them as query parameters to the DeonPay API.
    export function compact<T extends Record<string, unknown>>(obj: T): Partial<T> {
      const out: Record<string, unknown> = {};
      for (const [key, value] of Object.entries(obj)) {
        if (value === undefined || value === null) continue;
        if (typeof value === "string" && value.trim() === "") continue;
        out[key] = value;
      }
      return out as Partial<T>;
    }
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions return content (paginated results with fields) and amounts in centavos, but lacks information on idempotency, authorization needs, rate limits, or any side effects. The read-only nature is implied but not stated.

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

Conciseness4/5

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

The description is a single paragraph that front-loads the purpose and examples, then details filters and output. It could be slightly more concise, but every sentence contributes information. No redundancy.

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

Completeness4/5

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

Given 13 optional parameters and no output schema, the description covers most aspects: it lists all filter types, explains return fields, and notes pagination. Missing details include pagination iteration (e.g., next page hints) and exact response structure, but overall it's fairly complete.

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

Parameters5/5

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

Schema coverage is 69%, and the description adds significant value: it explains filter behavior (partial match for email, exact for merchant_reference, enum values for status/source_type/card_brand), date format (ISO 8601), and amount unit (centavos). This compensates for the schema gaps.

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 uses a specific verb-resource pair ('List transactions') and includes example queries that clarify scope. It differentiates itself from siblings like deonpay_get_transaction (single) and deonpay_list_link_transactions (link-specific).

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

Usage Guidelines4/5

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

The description provides explicit usage contexts via example queries and lists many filter options. However, it does not state when not to use this tool (e.g., for single transaction retrieval) or mention alternatives, though the sibling context implicitly fills that gap.

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/hectortemich/deonpay-mcp-server'

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