Skip to main content
Glama

Supplier bills due

list_bills_due
Read-onlyIdempotent

Use this when the user asks which supplier bills they owe, what is overdue to suppliers, or what they must pay in the next few days. Unpaid supplier bills that are overdue or due within days (default 30, up to 120): supplier, bill number, dates, amount, paid and remaining (after payments, supplier credits, advances and credit notes, as on the Bills page), with totals per currency split into overdue and not yet due (due_soon). Lists at most 50; when has_more is true, say how many there are. Unpaid bills without a due date are only counted. Needs access to expenses. Do not use it for money clients owe them (list_invoices with status overdue, list_clients).

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

Input Schema

NameRequiredDescriptionDefault
daysNoBills due within this many days from today, 0 to 120. Default 30.
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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), yet the description still adds real substance: the 50-row cap with has_more handling, how 'remaining' is computed after payments, credits, advances and credit notes, and that undated unpaid bills are counted but not listed. The one gap is that it does not say what happens when the expenses permission is missing (error vs empty result).

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?

Front-loaded with the use case, then scope, then output shape, then exclusions — a sensible ordering with almost no filler. The single dense paragraph is long but nearly every clause carries distinct information; splitting the exclusion clause out would improve scannability slightly.

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?

For a two-parameter read tool with no output schema, the description supplies return fields, currency-level totals split into overdue and due_soon, truncation behavior, and permission requirements. Nothing an agent needs to call or interpret the result is missing.

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 both parameters are already documented, and the description's 'default 30, up to 120' merely restates the schema. No additional meaning is added for business_id or the fallback when a single business is shared.

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 unpaid supplier bills due/overdue within N days) and enumerates the returned fields, so it is immediately distinguishable from invoice-facing siblings. The opening sentence frames the exact user question it answers.

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 explicit when-to-use triggers (which supplier bills are owed, what is overdue, what must be paid soon) and an explicit exclusion routing the agent to list_invoices with status overdue and list_clients for receivables. No inference required to pick this tool over its siblings.

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.

Resources