PocketQuota
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 |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| budget_statusA | Read today's quota, pool balances, overspend and insolvency status. Money returned in integer cents. |
| budget_transactionsC | Read dated journal entries, including reversals and automatic allocations. |
| budget_recordB | Record user-authorized expense, income or transfer. Default pool daily. Excess daily quota or exhausted daily pool is immediately covered by flex. Reuse request_id when retrying this same user request. |
| budget_reverseB | Reverse an incorrect manual transaction, preserving audit. Only on user authorization; do not silently delete or hide history. |
| budget_summaryA | Read expected pool balances and settlements for a day YYYY-MM-DD or completed month YYYY-MM. |
| budget_reconcileB | Record a user's explicitly supplied real balances. Never fabricate actual balances from expected values. Does not automatically adjust the ledger. |
| budget_notificationsA | List unacknowledged budget-exhausted notifications. Only notify the ledger owner through an authorized channel. Empty list means remain silent. Use event ID to deduplicate delivery. |
| budget_ack_notificationA | Acknowledge an event only AFTER successful owner notification. Failed delivery must remain pending. Use one designated notification agent per ledger. |
| budget_configureA | Requires manage scope and explicit user request. Change daily allowance or settlement/review times. Fetch budget_status first for settings.revision; effective date cannot be in the past. |
| budget_adjust_poolA | Requires manage scope and explicit user request. Set a pool's actual budget balance with an audit reason; this creates an adjustment entry, not a bank transfer. |
| budget_scheduleA | Requires manage scope and explicit user request. Create/edit/pause a daily or monthly credit schedule. Only accounting, not a payment. Existing schedule IDs come from budget_schedules. |
| budget_schedulesB | List recurring credit schedules and their IDs. |
| budget_settleA | Requires manage scope. Explicitly settle a day early; automatic settlement already runs on the server. Safe to retry with the same request_id. |
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 13 tools
Most tools target clearly distinct actions or resources, with readable boundaries between recording, reversing, settling, scheduling, and notification handling. Minor potential confusion exists between budget_status and budget_summary, and between budget_adjust_pool and budget_reconcile, though descriptions clarify the different effects.
All tools use a consistent budget_ prefix and snake_case. Suffixes mix nouns and verbs (budget_status, budget_record, budget_schedules, budget_ack_notification), which is readable but not a strict verb_noun pattern.
The 13 tools are well within a manageable range and each appears to serve a distinct budget/quota workflow. The set is neither thin nor bloated for a ledger-style server.
Core workflows are covered: status, transaction recording/reversal, summaries, reconciliation, scheduling, settlement, and notification acknowledgement. Minor gaps may exist around explicit pool lifecycle management and detailed single-record retrieval, but agents can work around them via existing list and adjustment tools.