Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Sync Integrations

flowcheck_sync

Trigger a full sync of all connected integrations and run reconciliation to detect issues and validate financial processes programmatically.

Instructions

Trigger a full sync of all connected integrations (Stripe, Shopify, Plaid) and run reconciliation. Returns which sources were synced, how many records were processed, and reconciliation results. Rate limited to 1 sync per 5 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the POST request to /sync on the FlowCheckClient.
    async () => {
      const result = await client.request("POST", "/sync");
      return { content: [{ type: "text" as const, text: result }] };
    },
  • src/tools/sync.ts:9-23 (registration)
    The registration block for the flowcheck_sync tool using server.registerTool.
    server.registerTool(
      "flowcheck_sync",
      {
        title: "Sync Integrations",
        description:
          "Trigger a full sync of all connected integrations (Stripe, Shopify, Plaid) " +
          "and run reconciliation. Returns which sources were synced, how many records " +
          "were processed, and reconciliation results. Rate limited to 1 sync per 5 minutes.",
        inputSchema: z.object({}),
      },
      async () => {
        const result = await client.request("POST", "/sync");
        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 the full burden of behavioral disclosure. It effectively describes key traits: it triggers an action ('Trigger a full sync'), specifies rate limits ('Rate limited to 1 sync per 5 minutes'), and outlines the outcome ('Returns which sources were synced, how many records were processed, and reconciliation results'). This covers operational constraints and expected behavior well.

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 front-loaded with the core action and scope, followed by return details and rate limits in a single, efficient sentence. Every part adds value without waste, making it easy to parse and understand quickly.

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 the tool's complexity (triggering syncs and reconciliation) and lack of annotations or output schema, the description does a good job explaining what the tool does, its constraints, and what it returns. However, it could be more complete by detailing error conditions or prerequisites (e.g., requiring connected integrations), but it covers the essentials adequately.

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 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately focuses on the tool's action and output without redundant parameter details, meeting the baseline for a parameterless tool.

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 specific action ('Trigger a full sync of all connected integrations') and resources involved ('Stripe, Shopify, Plaid'), distinguishing it from sibling tools that handle individual connections or other operations. It goes beyond just restating the name/title by specifying the scope and purpose.

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 implies usage context by mentioning 'all connected integrations' and 'run reconciliation', suggesting this tool is for batch synchronization rather than individual operations. However, it does not explicitly state when to use it versus alternatives like syncing individual sources or checking sync status, nor does it provide exclusions or prerequisites.

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