Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

List Transactions

flowcheck_list_transactions

Retrieve bank transactions from Plaid with date filtering and pagination. Deposits appear as negative amounts for financial analysis.

Instructions

List bank transactions from Plaid. Deposits appear as negative amounts. Filter by date range. Paginated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoStart date filter (YYYY-MM-DD)
toNoEnd date filter (YYYY-MM-DD)
limitNoResults per page (default 50, max 100)
cursorNoPagination cursor from previous response

Implementation Reference

  • The registration and handler logic for "flowcheck_list_transactions".
    server.registerTool(
      "flowcheck_list_transactions",
      {
        title: "List Transactions",
        description:
          "List bank transactions from Plaid. " +
          "Deposits appear as negative amounts. " +
          "Filter by date range. Paginated.",
        inputSchema: z.object({
          from: z
            .string()
            .optional()
            .describe("Start date filter (YYYY-MM-DD)"),
          to: z
            .string()
            .optional()
            .describe("End date filter (YYYY-MM-DD)"),
          limit: z
            .number()
            .min(1)
            .max(100)
            .optional()
            .describe("Results per page (default 50, max 100)"),
          cursor: z
            .string()
            .optional()
            .describe("Pagination cursor from previous response"),
        }),
      },
      async (params) => {
        const result = await client.request("GET", "/transactions", { params });
        return { content: [{ type: "text" as const, text: result }] };
      },
    );
Behavior3/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 adds useful context: deposits appear as negative amounts, filtering by date range is supported, and results are paginated. However, it doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or what the paginated response structure looks like, leaving gaps for a tool with no annotation coverage.

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 extremely concise and front-loaded, consisting of three short sentences that efficiently convey key information: what it does, a critical data quirk (negative deposits), and two behavioral traits (filtering, pagination). Every sentence earns its place with no wasted words.

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?

Given no annotations and no output schema, the description is incomplete for a tool with behavioral complexity. It covers basic functionality and some data semantics (negative deposits), but lacks details on authentication, error handling, response format, or pagination mechanics. For a list tool with pagination and no structured output, more context would be helpful.

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 fully documents all four parameters (from, to, limit, cursor). The description adds no additional parameter semantics beyond what's in the schema—it mentions filtering by date range and pagination, which are already covered by the schema's parameter descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose: listing bank transactions from Plaid. It specifies the resource (bank transactions) and source (Plaid), distinguishing it from siblings like flowcheck_get_balance or flowcheck_list_payouts. However, it doesn't explicitly differentiate from flowcheck_get_cashflow or flowcheck_list_discrepancies, which might also involve transaction data, leaving some ambiguity.

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 for listing transactions with date filtering and pagination, but provides no explicit guidance on when to use this tool versus alternatives like flowcheck_get_cashflow or flowcheck_list_discrepancies. It mentions filtering by date range, which suggests context, but lacks clear when/when-not instructions or named alternatives.

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/eliaskress/flow-check-financial-api-mcp-server'

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