Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Upgrade Plan

flowcheck_upgrade

Upgrade your FlowCheck plan to access more credits by creating a Stripe Checkout session for payment processing.

Instructions

Create a Stripe Checkout session to upgrade your plan. Returns a checkout URL the user must visit to complete payment. Plans: starter ($4.99/mo, 1,000 credits), growth ($19/mo, 5,000 credits), pro ($49/mo, 15,000 credits).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYesTarget plan to upgrade to

Implementation Reference

  • The handler implementation for the flowcheck_upgrade tool, which makes a request to the /billing/upgrade endpoint.
    async ({ plan }) => {
      const result = await client.request("POST", "/billing/upgrade", {
        body: { plan },
      });
      return { content: [{ type: "text" as const, text: result }] };
    },
  • The registration of the flowcheck_upgrade tool including its schema and handler.
    server.registerTool(
      "flowcheck_upgrade",
      {
        title: "Upgrade Plan",
        description:
          "Create a Stripe Checkout session to upgrade your plan. " +
          "Returns a checkout URL the user must visit to complete payment. " +
          "Plans: starter ($4.99/mo, 1,000 credits), growth ($19/mo, 5,000 credits), pro ($49/mo, 15,000 credits).",
        inputSchema: z.object({
          plan: z
            .enum(["starter", "growth", "pro"])
            .describe("Target plan to upgrade to"),
        }),
      },
      async ({ plan }) => {
        const result = await client.request("POST", "/billing/upgrade", {
          body: { plan },
        });
        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 behaviors: it creates a Stripe Checkout session (implying a mutation that initiates payment), returns a checkout URL (output format), and requires user action to complete payment. However, it doesn't mention authentication needs, rate limits, error conditions, or what happens if the user cancels.

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 output, followed by essential plan details. Both sentences earn their place: the first explains what the tool does and returns, the second provides critical pricing information. There is zero waste or redundancy.

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 no annotations and no output schema, the description does well by explaining the tool's purpose, output (checkout URL), and parameter semantics. However, for a mutation tool involving payment, it could better cover behavioral aspects like error handling, idempotency, or security requirements. It's mostly complete but has minor gaps.

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 100% description coverage, so the baseline is 3. The description adds significant value by listing the plan options with pricing and credit details (starter: $4.99/mo, 1,000 credits; growth: $19/mo, 5,000 credits; pro: $49/mo, 15,000 credits), which clarifies the meaning of the 'plan' parameter beyond the enum values in the schema.

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 Stripe Checkout session') and resource ('to upgrade your plan'), distinguishing it from sibling tools like flowcheck_topup (which likely adds credits) or flowcheck_register (which handles initial signup). It explicitly mentions payment and plan upgrades, 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 implies usage context by specifying it's for plan upgrades and listing available plans with pricing, but it doesn't explicitly state when to use this versus alternatives like flowcheck_topup or flowcheck_register. It provides clear prerequisites (user must have a plan to upgrade) but lacks explicit exclusions or named alternatives.

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