Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Register Account

flowcheck_register

Create a new FlowCheck account to access workflow analysis tools for detecting issues and validating financial processes. Returns a registration token and checkout URL.

Instructions

Create a new FlowCheck account. Returns a registration token and checkout URL. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail address for the new account

Implementation Reference

  • The implementation of the 'flowcheck_register' tool handler and registration within the registerAuthTools function.
    server.registerTool(
      "flowcheck_register",
      {
        title: "Register Account",
        description:
          "Create a new FlowCheck account. Returns a registration token and checkout URL. " +
          "No API key required.",
        inputSchema: z.object({
          email: z.string().email().describe("Email address for the new account"),
        }),
      },
      async ({ email }) => {
        const result = await client.request("POST", "/auth/register", {
          body: { email },
          noAuth: true,
        });
        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 effectively describes the action ('Create'), outcome ('Returns a registration token and checkout URL'), and a key constraint ('No API key required'), which are useful. However, it lacks details on permissions, rate limits, error handling, or whether the action is idempotent, leaving gaps 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.

Conciseness5/5

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

The description is extremely concise and front-loaded, with two sentences that efficiently convey the action, outcome, and a key constraint. Every word earns its place, and there is no redundant or verbose language, making it easy to parse 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 (a simple account creation with one parameter) and the lack of annotations and output schema, the description is reasonably complete. It covers the purpose, outcome, and a constraint, but could benefit from more behavioral details (e.g., response format or error cases) to fully compensate for the missing structured data.

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%, with the single parameter 'email' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides (e.g., format or validation rules), so it meets the baseline for high schema coverage without compensating with extra insights.

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 ('Create a new FlowCheck account') and resource ('account'), distinguishing it from siblings like 'flowcheck_get_registration_status' (which checks status) and 'flowcheck_connect_shopify' (which connects services). It explicitly mentions the outcome ('Returns a registration token and checkout URL'), making the purpose unambiguous.

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 clear context for when to use this tool ('Create a new FlowCheck account') and includes a helpful prerequisite ('No API key required'), which guides usage. However, it does not explicitly state when not to use it or name alternatives (e.g., 'flowcheck_get_registration_status' for checking existing accounts), missing full differentiation.

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