NitroWatch Billing Demo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_invoiceA | Fetch a single invoice by id |
| list_invoicesA | List all invoices, optionally filtered by account |
| send_invoiceB | Email an invoice to the customer. Can be voided and re-sent. |
| archive_customerA | Archive a customer account so it no longer appears in active listings |
| delete_accountA | Permanently delete a customer account and all associated invoices. Cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Health Checks | Current health status of all registered health checks |
| Widget Examples | Provides metadata and examples for all registered UI widgets |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: get_invoice retrieves a single invoice, list_invoices retrieves multiple, send_invoice emails an invoice, and archive_customer vs delete_account clearly separate soft from permanent customer removal. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern (get/list/send/archive/delete + resource). The use of 'get' for singular and 'list' for plural is conventional, and there is no mixing of styles.
With 5 tools, the server is well-scoped for a billing demo. It covers the essential operations without unnecessary bloat, and the count feels appropriate for its purpose.
The set covers invoice retrieval, emailing, and customer lifecycle (archive/delete), but lacks invoice creation, updating, or voiding. This is a minor gap for a billing system, but core workflows are still represented.