Footnote
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | Optional PostgreSQL connection URL. Omit for built-in SQLite sample data. | |
| PROVENANCE_DB | Yes | Path to the provenance database file. | |
| PROVENANCE_ACTOR | Yes | Name of the actor using the server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getOverdueInvoicesA | Returns every invoice for one customer that is past its due date and not fully paid, as of a given date, with the outstanding total. Aggregation is done in SQL. Use this for any question about what a customer owes. |
| getCustomerSummaryA | Returns master data for one customer plus their total open balance and open ticket count. Use this for "tell me about customer X" questions. |
| getPaymentHistoryA | Returns payments received from one customer since a given date, with the total. Use this for questions about whether or when a customer has paid. |
| getOpenTicketsA | Returns unresolved support tickets for one customer. Use this when assessing account risk or when a question asks why a customer might be unhappy or withholding payment. |
| getReceivablesAgingA | Returns the aging profile of all outstanding receivables as of a date, bucketed by days overdue. Use this for portfolio-level questions rather than single-customer ones. |
| verifyProvenanceChainA | Re-derives every hash in the provenance log and reports whether the trail has been modified since it was written. Returns the first inconsistency found, if any. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools mostly target clearly distinct operations: customer summary, overdue invoices, payment history, open tickets, aging, and provenance verification. There is some conceptual overlap between getOverdueInvoices and getCustomerSummary because both can answer balance-related questions, but the descriptions distinguish detailed invoice-level debt from a general customer overview.
Five of the six tools follow a consistent getNoun phrase pattern in camelCase, such as getOverdueInvoices and getCustomerSummary. verifyProvenanceChain is a minor verb-style deviation, but it remains clear and readable.
Six tools is a well-scoped set for a focused accounts-receivable and customer-support query server. Each tool appears to earn its place without unnecessary surface area.
The surface covers the core read-only workflows for customer financial health, support context, portfolio aging, and provenance. Minor gaps could include customer search/list operations or more detailed invoice/ticket lookups, but the essential questions in this domain are addressable.