Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Delete Webhook

flowcheck_delete_webhook

Remove a registered webhook endpoint from the FlowCheck Financial API MCP Server to stop receiving automated notifications.

Instructions

Remove a registered webhook endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWebhook endpoint ID

Implementation Reference

  • The registration and handler implementation for the flowcheck_delete_webhook tool.
    server.registerTool(
      "flowcheck_delete_webhook",
      {
        title: "Delete Webhook",
        description: "Remove a registered webhook endpoint.",
        inputSchema: z.object({
          id: z.string().describe("Webhook endpoint ID"),
        }),
      },
      async ({ id }) => {
        const result = await client.request("DELETE", `/webhooks/${id}`);
        return { content: [{ type: "text" as const, text: result }] };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove' implies a destructive operation, it doesn't specify whether this action is reversible, what permissions are required, what happens to associated data, or what the response looks like (success confirmation vs error).

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and understandable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no annotations and no output schema, the description is inadequate. It doesn't explain what 'removing' entails, what confirmation or data is returned, error scenarios, or dependencies on other tools. Given the complexity of webhook management, more context is needed.

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?

The schema has 100% description coverage, with the single parameter 'id' clearly documented as 'Webhook endpoint ID'. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline for high schema coverage.

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 ('Remove') and resource ('a registered webhook endpoint'), making the tool's purpose immediately understandable. However, it doesn't differentiate itself from potential alternatives or siblings beyond the obvious 'delete' vs 'create/list' distinction.

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 doesn't mention prerequisites (like needing an existing webhook ID), error conditions, or relationships with sibling tools like 'flowcheck_list_webhooks' or 'flowcheck_create_webhook'.

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