Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Create Webhook

flowcheck_create_webhook

Register HTTPS webhooks to receive real-time notifications for financial events like payouts, refunds, and balance changes, with HMAC-SHA256 verification for security.

Instructions

Register a new HTTPS webhook endpoint. Returns a signing secret for HMAC-SHA256 verification. Available events: payout.matched, payout.discrepancy, payout.missing, refund.detected, balance.threshold

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS webhook URL you own
eventsYesEvents to subscribe to

Implementation Reference

  • The handler function for the flowcheck_create_webhook tool.
    async ({ url, events }) => {
      const result = await client.request("POST", "/webhooks", {
        body: { url, events },
      });
      return { content: [{ type: "text" as const, text: result }] };
    },
  • The input schema defining the required parameters (url and events) for the flowcheck_create_webhook tool.
    inputSchema: z.object({
      url: z
        .string()
        .url()
        .describe("HTTPS webhook URL you own"),
      events: z
        .array(
          z.enum([
            "payout.matched",
            "payout.discrepancy",
            "payout.missing",
            "refund.detected",
            "balance.threshold",
          ]),
        )
        .describe("Events to subscribe to"),
    }),
  • The registration of the flowcheck_create_webhook tool using the MCP server.
    server.registerTool(
      "flowcheck_create_webhook",
      {
        title: "Create Webhook",
        description:
          "Register a new HTTPS webhook endpoint. " +
          "Returns a signing secret for HMAC-SHA256 verification. " +
          "Available events: payout.matched, payout.discrepancy, " +
          "payout.missing, refund.detected, balance.threshold",
        inputSchema: z.object({
          url: z
            .string()
            .url()
            .describe("HTTPS webhook URL you own"),
          events: z
            .array(
              z.enum([
                "payout.matched",
                "payout.discrepancy",
                "payout.missing",
                "refund.detected",
                "balance.threshold",
              ]),
            )
            .describe("Events to subscribe to"),
        }),
      },
      async ({ url, events }) => {
        const result = await client.request("POST", "/webhooks", {
          body: { url, events },
        });
        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. It discloses key behavioral traits: it returns a signing secret for HMAC-SHA256 verification and lists available events, which adds context beyond basic creation. However, it doesn't cover aspects like rate limits, error handling, or whether the operation 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 front-loaded with the core action and return value, followed by a concise list of events. Every sentence earns its place with no wasted words, making it efficient and easy to parse.

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 moderately complete for a creation tool. It covers the purpose and return value but lacks details on error cases, authentication requirements, or how the signing secret should be used, which are important for a webhook setup.

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 the parameters (url and events). The description adds minimal value by implying the URL must be HTTPS and owned by the user, but this is already covered in the schema's format and description. Baseline 3 is appropriate as 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 action ('Register a new HTTPS webhook endpoint') and resource ('webhook'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'flowcheck_list_webhooks' or 'flowcheck_delete_webhook' beyond the verb 'create' vs 'list/delete', missing a direct comparison.

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 by listing available events, suggesting it's for subscribing to specific financial events. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'flowcheck_list_webhooks' for viewing existing webhooks) or prerequisites like authentication needs.

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