AskRentAI

Analyze Aged Payables

analyze_aged_payables

Read-onlyIdempotent

Accounts-payable aging snapshot (AgedPayables, 79).

AP by aging bucket (Current / 1-30 / 31-60 / 61+), top GL accounts owed, and a focused list of GL accounts with 61+ day balances. Mirror image of analyze_aged_receivables. Scope to a single park or portfolio with portfolio / property_ids — the report honors PropertyIDs even though its CSV has no Property column for client-side filtering.

Slow when unscoped — a portfolio-wide first call takes 1-3 minutes. Scoping to a park or portfolio returns in seconds. Follow-up queries within 5 minutes are cached and return instantly.

Args: portfolio: Portfolio name or 3-letter prefix. property_ids: Comma-separated property IDs. Alternative to portfolio. as_of_date: MM/DD/YYYY for the as-of snapshot. Defaults to today. top_n: Number of top GL accounts to list (default 10, max 50).

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

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": "analyze_aged_payables"
  }
}

Input Schema

Name	Required	Description	Default
`top_n`	No
`location`	No
`portfolio`	No
`as_of_date`	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.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds valuable behavioral context: latency by scoping, caching duration, per-Location output labeling, and skipped-Location handling. The only minor omission is what happens on unreachable Locations, though 'listed as skipped' partially covers it.

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 purpose and scope, then performance, then args. It is information-dense, but the Location paragraph is fairly long and slightly repetitive with the earlier scoping sentence.

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?

An output schema exists, so return values needn't be explained, and the description still summarizes report contents. Combined with full parameter documentation and behavioral notes on latency and Location handling, nothing essential for correct invocation is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the burden — and it does. Every parameter (portfolio, property_ids, as_of_date with MM/DD/YYYY format, top_n with default 10/max 50, and location with its alternative forms) is documented with formats and semantics.

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 names a specific verb and resource (AP aging snapshot) and enumerates exactly what the report contains: aging buckets, top GL accounts owed, and a 61+ day list. It also explicitly differentiates itself from the sibling analyze_aged_receivables by calling itself its 'mirror image'.

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?

It clearly explains how to scope with portfolio vs property_ids, when each is appropriate, and how to use location with filter-by-ID cases. Performance guidance (1-3 minutes unscoped vs seconds scoped, plus 5-minute caching) tells the agent exactly how to call it efficiently.

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?