Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

List Webhooks

flowcheck_list_webhooks

View all registered webhook endpoints, their subscribed events, and current status to monitor integration points.

Instructions

List all registered webhook endpoints with their events and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registration and handler implementation for the "flowcheck_list_webhooks" tool.
    server.registerTool(
      "flowcheck_list_webhooks",
      {
        title: "List Webhooks",
        description: "List all registered webhook endpoints with their events and status.",
        inputSchema: z.object({}),
      },
      async () => {
        const result = await client.request("GET", "/webhooks");
        return { content: [{ type: "text" as const, text: result }] };
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool lists webhooks but doesn't disclose behavioral traits like whether it requires authentication, returns paginated results, or includes error handling. This is a significant gap for a tool with no annotation coverage.

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 that front-loads the core purpose ('List all registered webhook endpoints') and adds useful detail ('with their events and status') without any wasted words, making it easy for an agent to parse quickly.

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?

Given no annotations and no output schema, the description is incomplete. It lacks information on return values (e.g., format of listed webhooks), error conditions, or operational constraints, which are critical for an agent to use this tool effectively in a real-world context.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately adds no parameter details, avoiding redundancy. Baseline is 4 for 0 parameters, as it doesn't need to compensate for any schema gaps.

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 ('List all registered webhook endpoints') and the resources involved ('with their events and status'), distinguishing it from siblings like flowcheck_create_webhook or flowcheck_delete_webhook by focusing on retrieval rather than creation or deletion.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing registered webhooks first, or contrast with other listing tools like flowcheck_list_payouts or flowcheck_list_transactions, leaving the agent to infer usage context.

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