Skip to main content
Glama

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

List GL Accounts

list_gl_accounts
Read-onlyIdempotent

List the Rent Manager chart of accounts (GL accounts), grouped by type.

Use this to answer "what GL accounts / chart of accounts do we have", to find an account's number/ID, or before drilling into financials. Filter by account_type (e.g. "income", "expense") or name_filter (matches name or account number); active_only hides inactive accounts.

``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
locationNo
active_onlyNo
name_filterNo
account_typeNo

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.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds substantive behavior beyond them: output is grouped by type, results are labelled per Location, unreachable Locations are reported as skipped, and blank location resolves to all-or-single depending on the connection. That partial-failure and fan-out disclosure is exactly the context structured fields cannot carry.

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?

Use case and filters are front-loaded in the first two paragraphs with no wasted sentences. The location block is necessary given zero schema coverage, but its indented, blank-line-separated formatting is slightly awkward compared with the rest of the description.

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?

Four optional params, an output schema that covers return shape, and rich annotations — the description fills every remaining gap: filter semantics, location resolution, per-location labelling, and skipped-location reporting. Nothing an agent needs to call this correctly 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 coverage is 0%, so the description must carry all four parameters, and it does: account_type with concrete examples ('income', 'expense'), name_filter documented as matching name OR account number, active_only's hide-inactive behavior, and a full paragraph on location's three forms (ID, comma list, 'all') plus default semantics. It also warns that IDs belong to one Location, which is non-obvious and constraint-level useful.

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 ('List the Rent Manager chart of accounts (GL accounts), grouped by type') and immediately distinguishes itself from the analysis siblings by positioning itself as the lookup step 'before drilling into financials'. An agent can tell this apart from trial_balance or analyze_balance_sheet without opening any 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?

Gives three concrete use cases ('what GL accounts do we have', find an account's number/ID, before drilling into financials) plus explicit filter selection guidance for account_type vs name_filter and what active_only does. It also names the related tool (list_locations) an agent needs when location scoping is ambiguous.

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