Skip to main content
Glama

Aged creditors

crunch_get_aged_creditors
Read-only

Retrieves aged creditor balances owed to suppliers, grouped by age brackets and supplier, largest first, to identify overdue payables as of a chosen date.

Instructions

What the business owes suppliers and for how long: the outstanding balance of every unpaid or part-paid expense, grouped by age (0-30, 31-60, 61-90 and over 90 days since the expense date, since Crunch's expenses have no due date) and by supplier, largest first. Reads every expense up to the report date, so it can take a few seconds on a large account. details=true also lists each expense.

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

Input Schema

NameRequiredDescriptionDefault
detailsNoAlso list each outstanding record with its age (default false: totals only)
as_of_dateNoAge the balances as of this date (YYYY-MM-DD; default today)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, yet the description adds real behavioral detail: a full-table scan up to the report date with multi-second latency on large accounts, aging computed from expense date because Crunch expenses have no due date, and largest-first ordering. It stops short of describing whether supplier totals are net or gross or how zero balances are handled.

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?

Front-loaded with the core definition, then grouping, then the performance caveat, then the details flag. Three sentences with no filler; the long parenthetical about buckets and the missing due date carries necessary domain information.

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?

Two optional parameters, no output schema, and safe read-only annotations; the description supplies the grouping, ordering, latency, and the details expansion — enough for an agent to call it correctly and set expectations on runtime.

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 coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: that 'details=true lists each expense' is a per-record expansion of the same aging, and that the aging basis is the expense date rather than a due date, which explains what as_of_date actually shifts. Minor redundancy with the schema's own parameter text keeps it from a 5.

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?

It states a specific resource and verb: the outstanding balance of unpaid or part-paid expenses (money owed to suppliers), grouped by age bucket and supplier, sorted largest first. The 'owed to suppliers' framing inherently separates it from the aged-debtors sibling, and the report shape (buckets, grouping, ordering) is fully specified.

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?

Use is implied by the report definition, but it never says when to pick this over crunch_get_expenses_total or crunch_get_aged_debtors. The note that it reads every expense and may take a few seconds is useful cost context, though it is not explicit when/when-not guidance.

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

Deploy Server

Other Tools