Skip to main content
Glama

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

Trial Balance

trial_balance
Read-onlyIdempotent

Trial balance — every GL account's debit/credit activity and ending balance.

Runs RM's TrialBalanceActivity (report 617) with a built-in balance check (total debits = total credits; ending balances sum to ~0 for a full scope). Use for "show the trial balance", "ending balance per GL account", "are the books in balance / do debits equal credits". Scopes via PropOwnerIDs (portfolio or property_ids). Defaults to YTD; override with start_date/ end_date (MM/DD/YYYY). Filter with account_filter; nonzero_only hides no-activity zero-balance accounts. Pairs with list_gl_accounts. For transaction-level GL detail, download report 51 (GeneralLedger) via run_report.

``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
nonzero_onlyNo
property_idsNo
account_filterNo

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

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that it runs report 617, performs a debit/credit balance check, defaults to YTD, expects MM/DD/YYYY dates, hides no-activity zero-balance accounts with nonzero_only, and explains location behavior including skipped unreachable locations and labeled output. These are meaningful operational details not supplied by the readOnly/idempotent annotations.

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

Conciseness5/5

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

The description is front-loaded with purpose and usage, then adds relevant operational details in a compact structure. The location paragraph is longer but every clause provides useful invocation context, especially around default location behavior and unreachable locations.

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

Completeness4/5

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

Given the output schema and rich annotations, the description is nearly complete: it covers purpose, usage, report behavior, defaults, location handling, and most parameter effects. The remaining gap is insufficient detail on portfolio/property_ids and account_filter formats, which matters because the input schema provides no descriptions.

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

Parameters4/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 parameter meaning, and it does document date format/defaults, location semantics, nonzero_only behavior, account_filter, and portfolio/property_ids scoping. However, it does not explain the expected format for portfolio or property_ids, nor the syntax accepted by account_filter, so it does not fully compensate for the empty schema descriptions.

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 the exact report and output content: "every GL account's debit/credit activity and ending balance," plus the built-in balance check. It clearly distinguishes this report from transaction-level GL detail by pointing to report 51 via run_report. An agent can identify the tool's purpose without opening the 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?

The description gives explicit use cases ("show the trial balance," "ending balance per GL account," "are the books in balance / do debits equal credits") and names the alternative for transaction-level GL detail. It also states scoping, default date behavior, and pairing with list_gl_accounts, leaving little to inference.

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