Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Get Balance

flowcheck_get_balance

Retrieve combined financial balances from Stripe and bank accounts in a single API call, providing available and pending amounts in USD cents for workflow analysis.

Instructions

Get combined Stripe and bank balances in one call. Returns available/pending Stripe balance and Plaid bank balance. All amounts are in cents (USD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that calls the FlowCheckClient to fetch the balance from the API and returns the result as text.
    async () => {
      const result = await client.request("GET", "/balance");
      return { content: [{ type: "text" as const, text: result }] };
    },
  • Schema definition for the flowcheck_get_balance tool, including title, description, and an empty input schema.
    {
      title: "Get Balance",
      description:
        "Get combined Stripe and bank balances in one call. " +
        "Returns available/pending Stripe balance and Plaid bank balance. " +
        "All amounts are in cents (USD).",
      inputSchema: z.object({}),
    },
  • Tool registration block for flowcheck_get_balance within the registerBalanceTools function.
    server.registerTool(
      "flowcheck_get_balance",
      {
        title: "Get Balance",
        description:
          "Get combined Stripe and bank balances in one call. " +
          "Returns available/pending Stripe balance and Plaid bank balance. " +
          "All amounts are in cents (USD).",
        inputSchema: z.object({}),
      },
      async () => {
        const result = await client.request("GET", "/balance");
        return { content: [{ type: "text" as const, text: result }] };
      },
    );
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it combines multiple data sources (Stripe and bank via Plaid), returns specific balance types (available/pending), and specifies currency units (cents in USD). However, it doesn't mention rate limits, authentication needs, or error conditions.

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 perfectly concise with three tightly packed sentences that each add essential information: what it retrieves, what data it returns, and currency details. Zero wasted words.

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?

For a zero-parameter tool with no annotations and no output schema, the description provides excellent context about what data is returned and in what format. It could be more complete by mentioning authentication requirements or typical response structure, but covers the essentials well.

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

Parameters4/5

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

The tool has zero parameters with 100% schema coverage, so the baseline is 4. The description appropriately adds no parameter information since none exist, focusing instead on what the tool returns.

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 clearly states the tool's purpose with specific verbs ('Get combined Stripe and bank balances') and resources ('Stripe and bank balances'), distinguishing it from siblings like flowcheck_get_cashflow or flowcheck_get_position by specifying the exact balance types returned.

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 retrieving combined financial balances, but doesn't explicitly state when to use this tool versus alternatives like flowcheck_get_cashflow or flowcheck_get_position. No guidance on prerequisites or exclusions is provided.

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