Skip to main content
Glama
Sign In

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

Analyze Aged Receivables

analyze_aged_receivables
Read-onlyIdempotent

Aged receivables (30 / 31-60 / 61-90 / 91+) for a portfolio.

Pulls AgedReceivables (78), aggregates per property, ranks delinquent tenants. Answers: 'who's most past-due', 'how much is 90+ days old', 'what's our total AR for the Main Street portfolio'.

``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_receivables"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNo
locationNo
portfolioNo
as_of_dateNo
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

B3.4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: it pulls AgedReceivables (78), aggregates per property, ranks delinquent tenants, labels output per Location, and notes that unreachable Locations are skipped.

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, aging buckets, aggregation behavior, and example questions. The location guidance is detailed but useful; some formatting and backtick usage is awkward, yet no major sentence is wasted.

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 not be described. Annotations cover the safety profile. However, with five parameters and 0% schema description coverage, the description is incomplete because it only explains location and leaves the other four parameters ambiguous.

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%, so the description must carry the burden for five parameters. It explains location thoroughly, including comma-separated lists, 'all', and blank behavior, but top_n, portfolio, as_of_date, and property_ids are not described or clarified. This leaves most parameters undocumented.

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 states a specific resource (aged receivables), the aging buckets (30 / 31-60 / 61-90 / 91+), and the analytical output (aggregated per property, ranked delinquent tenants). It gives example questions that clarify the intended analysis. It does not explicitly differentiate itself from close siblings such as analyze_delinquency, but the purpose is otherwise clear.

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?

The description explains how the optional location parameter behaves, including blank/default behavior and multi-location labeling. However, it does not explicitly say when to use this tool versus analyze_delinquency or analyze_rent_roll, nor does it state exclusions or prerequisites beyond location handling.

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