Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Finance: Cash flow

fin_cashflow
Read-only

When money is expected to move, and whether it will be there: a running balance per currency over a window, the lowest point it reaches, and every day it goes negative. Answers 'will we have enough on the 20th' and 'where is the cash gap'. Per currency on purpose — hryvnia on hand does not cover a payment due in euro, so never add the currencies together when reporting this. An opening balance the system could not read is flagged rather than assumed to be zero.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fin_cashflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoStart date YYYY-MM-DD. Default: today.
untilNoEnd date YYYY-MM-DD. Default: +90 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only and non-destructive behavior, so the description focuses on domain-specific traits: per-currency separation and flagging an unread opening balance instead of assuming zero. These are meaningful behavioral disclosures beyond the annotations, though pagination and error-handling details are not covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core concept and every sentence carries useful meaning, including the per-currency warning and the opening-balance flag. The narrative opening is slightly indirect, but the overall structure remains clear and efficient.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of explaining return semantics, and it does so by listing the running balance, lowest point, negative days, per-currency handling, and opening-balance flag. For a simple two-parameter read-only query, this is complete enough for an agent to call correctly.

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?

Schema description coverage is 100%, with since and until already documented including their defaults. The description refers to a window but adds no syntax, formatting, or date-boundary semantics beyond what the schema provides, so the baseline score of 3 applies.

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 what the tool returns: a running balance per currency over a window, the lowest point reached, and days going negative. It is specific about the resource and scope, but it does not explicitly distinguish itself from sibling tools such as fin_upcoming_obligations or fin_overview.

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?

It gives concrete usage scenarios ('will we have enough on the 20th' and 'where is the cash gap') and a clear reporting constraint about not adding currencies together. However, it does not name alternatives or state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OrgLines toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources