Expense Claim Helper
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_tripC | Write an itinerary with ISO times; identical input reuses the trip. |
| add_expenseC | Write an expense and copy an optional local receipt. Money is a decimal string. |
| check_missingC | Read missing/orphan files, amount mismatches and duplicate/unmatched warnings. |
| build_claimC | Write immutable claim snapshots and local reports; reserve claimed items. |
| list_pending_claimsC | Read reminders, unpaid amounts and employee advance balance. |
| travel_daysB | Read annual local-calendar travel days, capped at one day per date. |
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
Each tool targets a clearly distinct action or resource: adding trips, adding expenses, validating missing items, building claims, listing pending claims, and calculating travel days. There is no overlap in purpose, and the boundary between write operations (add_trip, add_expense, build_claim) and read operations (check_missing, list_pending_claims, travel_days) is clear.
Most tool names follow a predictable verb_noun pattern (add_trip, add_expense, check_missing, build_claim, list_pending_claims). The only deviation is travel_days, which is a noun phrase rather than a verb-led name, but it remains readable and unambiguous.
Six tools is well within the typical 3–15 range for a focused workflow assistant. Each tool appears to earn its place by covering a distinct step in the expense claim lifecycle, with no obviously redundant tools.
The surface covers creating trips and expenses, checking for issues, building claim snapshots, listing pending claims, and calculating travel days. However, there are no update or delete operations for trips or expenses, and no way to read or list individual existing records beyond aggregated warnings and pending summaries, leaving notable lifecycle gaps.