Skip to main content
Glama

Aged creditors

accounting_aged_creditors
Read-onlyIdempotent

Aged creditors (what the business owes suppliers, by age) as at a date, reconciled to Accounts Payable. 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_creditors"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description's added value is the authentication model ('they are asked to sign in the first time') and the fact that figures reconcile to Accounts Payable. It stops short of describing result structure or failure modes.

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: definition first, safety second, prerequisite last. No filler and nothing buried.

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?

For a zero-required-parameter reporting tool with no output schema, the description should at least hint at the aging buckets or the shape of the report and what 'reconciled to Accounts Payable' entails. All parameters are optional with sensible defaults, which lowers the burden, but the return content remains undescribed.

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 description coverage is 100%, with defaults and the due/invoice enum fully documented inline, so the schema carries parameter meaning. The description adds nothing about as_at, basis, or business_id beyond what the schema already says.

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?

States a specific resource and defines it in plain terms ('what the business owes suppliers, by age'), plus a reconciliation scope, so it is clearly distinguishable from accounting_aged_debtors even though that sibling is not named explicitly.

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?

Usage is implied by the definition (you call this when you need supplier aging), and a useful prerequisite is stated (GetAccountED sign-in). However, there is no explicit when-to-use vs accounting_trial_balance / accounting_general_ledger / accounting_reconciliation_status guidance and no exclusions.

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.