Skip to main content
Glama

What's due

get_whats_due
Read-onlyIdempotent

Use this when the user asks what needs attention: overdue invoices, bills to pay, the next VAT return and its deadline, or tax warnings ("what's due this week?"). What needs paying or filing: overdue sales invoices (remaining above 0 and past the due date), unpaid supplier bills due within days (default 14, overdue bills included; needs access to bills), the next VAT return not yet marked filed, past VAT periods not marked filed, each with its filing deadline (period end + 28 days, moved to the next UAE working day), vat_estimate (the VAT report's net so far for the next return: an estimate from the documents in Fatura Go, not a figure to file) and warnings (at most two, ranked; any penalty comes with its official source and checked date, so keep those with the amount). When warnings_check is "unavailable", warnings and more_warnings are null and vat_estimate is null: that part could not be checked, which does not mean there is nothing to report. Each list has count (the full total), listed and has_more: when has_more is true, say how many there are and do not present the list as complete. Do not use it for the full list of supplier bills (list_bills_due) or for VAT figures by box (get_vat_return_boxes).

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

Input Schema

NameRequiredDescriptionDefault
daysNoBills due within this many days from today, 0 to 60. Default 14.
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.8/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description goes well beyond them: it defines the overdue predicate (remaining above 0 and past the due date), the filing-deadline computation (period end + 28 days, shifted to the next UAE working day), a degraded mode (warnings_check="unavailable" nulls warnings and vat_estimate and does not mean nothing is due), and list truncation semantics (count vs listed vs has_more, with instructions not to present a partial list as complete). No output schema exists, so this disclosure carries the return-shape burden entirely.

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?

It is front-loaded with the trigger scenario and closes with the exclusions, and nearly every clause carries operational information. The middle section is a single dense paragraph of semicolon- and parenthesis-nested clauses that is harder to scan than it needs to be, though little is genuinely redundant.

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 read-only aggregate with two optional parameters and no output schema, everything needed to call and interpret it is present: what each list contains, how counts and has_more behave, when fields go null, and how much to trust vat_estimate (an estimate, not a filing figure). Nothing material is left for the agent to guess.

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 the baseline is 3. The description still adds real meaning for `days` by stating the default (14) and that overdue bills are included, which the schema does not say. The `business_id` parameter is left entirely to the schema, keeping this short of 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?

The description names a precise resource set: overdue sales invoices, unpaid supplier bills within N days, the next unfiled VAT return, past unfiled VAT periods, vat_estimate and warnings. It also explicitly distinguishes itself from list_bills_due and get_vat_return_boxes, so an agent can separate it from the closest siblings 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?

Usage is triggered by concrete user phrasing ("what's due this week?", "what needs attention") and exclusions are stated with named alternatives ("Do not use it for the full list of supplier bills (list_bills_due) or for VAT figures by box (get_vat_return_boxes)"). Both the when and the when-not are explicit.

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