Skip to main content
Glama
eliaskress

FlowCheck Financial API MCP Server

by eliaskress

Financial Position

flowcheck_get_position

Retrieve a 7-day financial summary including balances, cash flow, health score, and open discrepancies to analyze financial position and detect issues.

Instructions

Get a 7-day financial summary designed for AI agents. Returns balances, payout counts, cash flow, health score, and open discrepancies in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the flowcheck_get_position tool, which fetches data from the /agent/position endpoint.
    async () => {
      const result = await client.request("GET", "/agent/position");
      return { content: [{ type: "text" as const, text: result }] };
    },
  • Tool registration for flowcheck_get_position within the registerAgentTools function.
    server.registerTool(
      "flowcheck_get_position",
      {
        title: "Financial Position",
        description:
          "Get a 7-day financial summary designed for AI agents. " +
          "Returns balances, payout counts, cash flow, health score, " +
          "and open discrepancies in a single call.",
        inputSchema: z.object({}),
      },
      async () => {
        const result = await client.request("GET", "/agent/position");
        return { content: [{ type: "text" as const, text: result }] };
      },
    );
Behavior3/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 discloses the 7-day timeframe and that it returns aggregated data (summary), which are useful behavioral traits. However, it lacks details on authentication needs, rate limits, error handling, or whether it's read-only (implied by 'Get' but not explicit).

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, well-structured sentence that front-loads the core action ('Get a 7-day financial summary') and efficiently lists key outputs. Every word adds value without redundancy, making it highly concise 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 the tool has no parameters, no annotations, and no output schema, the description provides a clear purpose and output scope. However, it lacks details on behavioral aspects like authentication or error handling, and doesn't fully address how it differs from sibling tools, leaving some gaps in context for an AI agent.

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 documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and output. A baseline of 4 is applied as it compensates for the lack of parameters by describing the output scope.

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 tool's purpose: 'Get a 7-day financial summary' with specific outputs (balances, payout counts, etc.). It uses a specific verb ('Get') and resource ('financial summary'), but doesn't explicitly differentiate from siblings like 'flowcheck_get_balance' or 'flowcheck_get_cashflow' which appear to provide more granular data.

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 mentions the summary is 'designed for AI agents' and returns multiple data points 'in a single call', which implies efficiency benefits. However, it provides no explicit guidance on when to use this tool versus alternatives like the sibling tools that fetch individual components (e.g., 'flowcheck_get_balance'), nor any prerequisites or exclusions.

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