Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

Connect Stripe

flowcheck_connect_stripe

Connect a Stripe account to FlowCheck Financial API using a restricted API key with read access to Payouts and Balance. The key is encrypted with AES-256-GCM for secure integration.

Instructions

Connect a Stripe account using a restricted API key. The key must have read access to Payouts and Balance. FlowCheck encrypts it with AES-256-GCM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
restricted_keyYesStripe restricted API key (rk_live_... or rk_test_...)

Implementation Reference

  • src/tools/connect.ts:23-28 (handler)
    Handler for the flowcheck_connect_stripe tool, which sends a request to the /connect/stripe endpoint.
    async ({ restricted_key }) => {
  const result = await client.request("POST", "/connect/stripe", {
    body: { restricted_key },
  });
  return { content: [{ type: "text" as const, text: result }] };
},
  • src/tools/connect.ts:17-21 (schema)
    Input schema definition for the flowcheck_connect_stripe tool.
    inputSchema: z.object({
  restricted_key: z
    .string()
    .describe("Stripe restricted API key (rk_live_... or rk_test_...)"),
}),
  • src/tools/connect.ts:9-29 (registration)
    Registration of the flowcheck_connect_stripe tool within the McpServer.
    server.registerTool(
  "flowcheck_connect_stripe",
  {
    title: "Connect Stripe",
    description:
      "Connect a Stripe account using a restricted API key. " +
      "The key must have read access to Payouts and Balance. " +
      "FlowCheck encrypts it with AES-256-GCM.",
    inputSchema: z.object({
      restricted_key: z
        .string()
        .describe("Stripe restricted API key (rk_live_... or rk_test_...)"),
    }),
  },
  async ({ restricted_key }) => {
    const result = await client.request("POST", "/connect/stripe", {
      body: { restricted_key },
    });
    return { content: [{ type: "text" as const, text: result }] };
  },
);

Tool Definition Quality

B3.2/5.0
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 some context: the tool encrypts the key with AES-256-GCM, which hints at security handling, and specifies required permissions (read access to Payouts and Balance). However, it lacks details on outcomes (e.g., what happens after connection, error conditions, or side effects), which is a gap for a mutation tool.

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 concise and front-loaded, with two sentences that directly address the tool's purpose and key details. There's no wasted text, though it could be slightly more structured by separating usage instructions from behavioral notes.

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 the tool's complexity (a mutation with security implications), no annotations, and no output schema, the description is incomplete. It covers the basic action and encryption but misses critical details like response format, error handling, and integration context, making it only minimally adequate.

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 already documents the parameter 'restricted_key' with its type and format. The description adds marginal value by reiterating the key type and required permissions, but doesn't provide additional semantics beyond what the schema specifies, such as validation rules or examples.

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 action ('Connect a Stripe account') and the method ('using a restricted API key'), which is specific and actionable. However, it doesn't explicitly differentiate this tool from sibling tools like 'flowcheck_connect_shopify' or 'flowcheck_register', which might also involve account connections or registrations.

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 provides no guidance on when to use this tool versus alternatives. It mentions the key requirements but doesn't specify prerequisites, context (e.g., initial setup vs. reconnection), or exclusions, leaving the agent to infer usage from the tool name alone.

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