Skip to main content
Glama

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

Analyze Cash Flow

analyze_cash_flow
Read-onlyIdempotent

Indirect-method cash flow per property (CashFlow, report 54).

Net Income, total adjustments, net change in cash. Adjustments bucketed by Account Type (Other Current Asset/Liability, Fixed Asset, Long Term Liability, Equity). show_detail=True breaks out per-property adjustment lines.

``location`` (optional): a Rent Manager Location ID, a comma-separated
list, or ``"all"`` to run across every Location on this connection (see
``list_locations``). Blank = all Locations if the connection has several,
else its only Location. Output is labelled per Location; a Location that
can't be reached is listed as skipped. IDs (property, tenant, ...) belong
to one Location, so pass that Location when you filter by one.

Input Schema

NameRequiredDescriptionDefault
end_dateNo
locationNo
portfolioNo
start_dateNo
show_detailNo
property_idsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location
      Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context: report number, indirect method, adjustment bucketing, show_detail behavior, and location fallback/skipped-location handling. It stops short of covering date-range or portfolio behavior, so it is strong but not complete.

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 core purpose is front-loaded and the location paragraph is structured around defaults and output behavior. The location discussion is somewhat long, but most of it earns its place because the schema provides no parameter descriptions.

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?

The tool has annotations and an output schema, which reduce the description's burden, and location behavior is well covered. However, for a six-parameter financial report with zero schema description coverage, missing date-range, portfolio, and property_ids semantics leave meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for six parameters. The description explains location in detail and show_detail partially, but says nothing about start_date, end_date, portfolio, or property_ids, leaving most parameters undocumented.

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 opens with a specific verb/resource and reporting method: 'Indirect-method cash flow per property (CashFlow, report 54).' It also lists the report's core components, making it distinguishable from siblings like analyze_noi, analyze_financials, and analyze_balance_sheet.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful guidance for show_detail and location behavior, but does not explicitly say when to choose this tool over related financial-analysis siblings such as analyze_noi or analyze_financials. Usage is implied by the financial-report context rather than routed explicitly.

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

All AskRentAI 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