AskRentAI

Analyze Financials

analyze_financials

Read-onlyIdempotent

Detailed single-period financial breakdown with per-account line items (when show_detail=True). Pulls the standard ProfitLoss report (report 43).

Provides line-item detail for a single period (an audit-style breakdown), matching "the standard P&L statement" / "the regular P&L". General "P&L", "Profit and Loss" and "T12" views come from analyze_pl_trend, which runs the 12-month recap report (ProfitLossRecapMonth), the default P&L view for this product.

``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

Name	Required	Description	Default
`end_date`	No
`location`	No
`portfolio`	No
`start_date`	No
`show_detail`	No
`property_ids`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / location

Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety bar is low; the description adds genuinely useful traits: detail lines only appear with show_detail=True, output is labelled per Location, unreachable Locations are reported as skipped, and IDs belong to exactly one Location. It stops short of noting date-range defaults or rate limits, but that is minor.

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?

Scope and report ID are front-loaded, then the sibling differentiation, then parameter notes — a sensible order. A few phrases are redundant ("the standard P&L statement" / "the regular P&L" quoted twice, the parenthetical audit-style gloss) and the indentation is idiosyncratic, but nothing is genuinely wasteful.

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?

An output schema exists, so return values need no explanation, and the location-selection behavior is well covered for a multi-location connection. However, with six parameters, zero schema coverage, and no description of date-range or portfolio/property_ids semantics, an agent can call it but not confidently predict how periods or portfolio filters will be applied.

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 coverage is 0%, so the description must compensate. It does so thoroughly for `location` (ID, CSV list, "all", blank-default semantics, interaction with filtered IDs) and mentions show_detail, but start_date, end_date, portfolio and property_ids receive no semantic explanation at all — even something as basic as whether dates are inclusive or what format portfolio/property_ids take.

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?

States a specific verb and resource — a detailed single-period financial breakdown from the standard ProfitLoss report (report 43) — and explicitly names the sibling it differs from (analyze_pl_trend / ProfitLossRecapMonth). An agent can distinguish this from the other ~30 analyze_* tools without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes queries: general "P&L", "Profit and Loss" and "T12" views belong to analyze_pl_trend, while this tool serves "the standard P&L statement" / "the regular P&L" and audit-style single-period breakdowns. That is a concrete when-to-use / when-to-use-something-else rule.

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

All AskRentAI tools Inspect

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

Need Help?