Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Create Plaid Link Token

flowcheck_create_plaid_link_token

Generate a Plaid Link token to securely connect bank accounts in web applications, enabling financial data access for workflow validation.

Instructions

Create a Plaid Link token to initiate bank connection in the browser. Use the returned link_token with the Plaid Link SDK.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the tool "flowcheck_create_plaid_link_token" in src/tools/connect.ts.
    server.registerTool(
      "flowcheck_create_plaid_link_token",
      {
        title: "Create Plaid Link Token",
        description:
          "Create a Plaid Link token to initiate bank connection in the browser. " +
          "Use the returned link_token with the Plaid Link SDK.",
        inputSchema: z.object({}),
      },
  • The handler implementation for the "flowcheck_create_plaid_link_token" tool.
    async () => {
      const result = await client.request(
        "POST",
        "/connect/plaid/link-token",
      );
      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 that this tool creates a token for initiating bank connections, implying a write operation, but lacks details on permissions, rate limits, or error handling. It adds some context about the token's use with the Plaid Link SDK, but more behavioral traits would be helpful.

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 purpose in the first sentence and adds necessary usage guidance in the second. Both sentences earn their place by providing essential information without redundancy, making it efficiently structured and concise.

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 (creating a token for bank connections) and lack of annotations and output schema, the description is adequate but incomplete. It explains the purpose and next steps but omits details like response format, error cases, or prerequisites, which would enhance completeness for this type of operation.

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 does not discuss parameters, focusing instead on the tool's purpose and usage, which aligns with the baseline score for zero parameters.

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 Plaid Link token') and the resource ('to initiate bank connection in the browser'), distinguishing it from siblings like flowcheck_exchange_plaid_token. It precisely defines what the tool does without being vague or tautological.

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 ('to initiate bank connection in the browser') and mentions the next step ('Use the returned link_token with the Plaid Link SDK'), but does not explicitly state when not to use it or name alternatives like flowcheck_exchange_plaid_token for comparison.

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