Skip to main content
Glama

Aged debtors

accounting_aged_debtors
Read-onlyIdempotent

Aged debtors (who owes the business, by age: not yet due, 1-30, 31-60, 61-90, 91-120, 120+ days past due) as at a date, reconciled to Accounts Receivable. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

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

Input Schema

NameRequiredDescriptionDefault
as_atNoYYYY-MM-DD (default today)
basisNoAge from due date (default) or invoice date
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context beyond them: the sign-in requirement via GetAccountED and the first-time sign-in prompt, plus the fact the figures are reconciled to Accounts Receivable. It does not describe output shape or whether reconciliation can fail, which keeps it from a 5.

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?

Three short sentences with zero filler: purpose and bucket definition first, read-only status and reconciliation next, prerequisite last. Every clause carries information an agent would otherwise have to infer.

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?

With no output schema, the description carries return-shape duty, and it does reasonably well by enumerating the aging buckets and stating reconciliation to Accounts Receivable. It leaves the caller without any sense of whether the result is a totals table or per-debtor rows, a minor gap for a simple three-optional-parameter read tool.

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 100%, so all three parameters are already documented, and the description only restates the as-at date concept and the age-bucket definitions. It adds no syntax, format, or edge-case detail (e.g. an as_at in the future, or basis interacting with the buckets) beyond the schema. Baseline 3 is the correct ceiling here.

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?

Names the exact resource ('Aged debtors'), defines what it measures ('who owes the business') and enumerates the age buckets returned. The parenthetical makes it unmistakably distinct from accounting_aged_creditors without needing to open either schema.

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

Usage Guidelines4/5

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

Clear usage context: point-in-time reporting as at a date, with the due-vs-invoice basis choice implied by the parameter surface, and the business_id note pointing to accounting_list_my_businesses when a practice wants another client's books. It does not state exclusions or explicitly route an agent away from accounting_aged_creditors or accounting_general_ledger, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.