helpdesk
by karnstack
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELPDESK_DB | No | Path to the SQLite database for the local stdio server. | |
| HELPDESK_USER | No | The user for the local stdio server. | |
| BILLING_API_KEY | No | API key for the billing provider. Default: a test key. | |
| EXPORT_DELAY_MS | No | Delay in milliseconds per batch for export_tickets. Default: 250 ms a batch. | |
| HELPDESK_STATE_KEY | No | At least 32 bytes; used to sign requestState. Default: random per process. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ticketsA | Search support tickets by words in the subject or messages, 50 per page, most recently updated first. Returns ticket number, subject, status and customer id for every ticket it finds. |
| get_ticketA | Fetch one support ticket by its number, with subject, status, customer id and the customer's messages. Ticket numbers are digits only, for example 2318. |
| get_customerA | Fetch one customer account (a gym or a yoga studio) with its plan, contact email and recent charges. Customer ids start with cus_, for example cus_1042. |
| export_ticketsA | Export tickets to a CSV file. Slow for large exports; reports progress. Returns an export id for the file. |
| add_internal_noteA | Add an internal note to a ticket. Only staff see notes, never the customer. Each call adds a new note. |
| issue_refundA | Refund a customer's charge for a ticket through the billing provider, after the user confirms. Safe to retry: one ticket and charge are refunded at most once. Amounts are in cents. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_ticket | Read one ticket with the refund policy and propose the next step. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| refund_policy | When support may refund a customer, and how much. Read before any refund. |
| ticket 2331 | One support ticket as JSON, with the customer's messages. |
| ticket 2262 | One support ticket as JSON, with the customer's messages. |
| ticket 2298 | One support ticket as JSON, with the customer's messages. |
| ticket 2132 | One support ticket as JSON, with the customer's messages. |
| ticket 2044 | One support ticket as JSON, with the customer's messages. |
| ticket 2066 | One support ticket as JSON, with the customer's messages. |
| ticket 2124 | One support ticket as JSON, with the customer's messages. |
| ticket 2330 | One support ticket as JSON, with the customer's messages. |
| ticket 2117 | One support ticket as JSON, with the customer's messages. |
| ticket 2312 | One support ticket as JSON, with the customer's messages. |
| ticket 2254 | One support ticket as JSON, with the customer's messages. |
| ticket 2237 | One support ticket as JSON, with the customer's messages. |
| ticket 2305 | One support ticket as JSON, with the customer's messages. |
| ticket 2238 | One support ticket as JSON, with the customer's messages. |
| ticket 2112 | One support ticket as JSON, with the customer's messages. |
| ticket 2189 | One support ticket as JSON, with the customer's messages. |
| ticket 2281 | One support ticket as JSON, with the customer's messages. |
| ticket 2075 | One support ticket as JSON, with the customer's messages. |
| ticket 2244 | One support ticket as JSON, with the customer's messages. |
| ticket 2060 | One support ticket as JSON, with the customer's messages. |
| ticket 2213 | One support ticket as JSON, with the customer's messages. |
| ticket 2321 | One support ticket as JSON, with the customer's messages. |
| ticket 2258 | One support ticket as JSON, with the customer's messages. |
| ticket 2294 | One support ticket as JSON, with the customer's messages. |
| ticket 2198 | One support ticket as JSON, with the customer's messages. |
| ticket 2328 | One support ticket as JSON, with the customer's messages. |
| ticket 2329 | One support ticket as JSON, with the customer's messages. |
| ticket 2250 | One support ticket as JSON, with the customer's messages. |
| ticket 2173 | One support ticket as JSON, with the customer's messages. |
| ticket 2015 | One support ticket as JSON, with the customer's messages. |
| ticket 2082 | One support ticket as JSON, with the customer's messages. |
| ticket 2247 | One support ticket as JSON, with the customer's messages. |
| ticket 2176 | One support ticket as JSON, with the customer's messages. |
| ticket 2113 | One support ticket as JSON, with the customer's messages. |
| ticket 2181 | One support ticket as JSON, with the customer's messages. |
| ticket 2019 | One support ticket as JSON, with the customer's messages. |
| ticket 2055 | One support ticket as JSON, with the customer's messages. |
| ticket 2126 | One support ticket as JSON, with the customer's messages. |
| ticket 2081 | One support ticket as JSON, with the customer's messages. |
| ticket 2229 | One support ticket as JSON, with the customer's messages. |
| ticket 2035 | One support ticket as JSON, with the customer's messages. |
| ticket 2077 | One support ticket as JSON, with the customer's messages. |
| ticket 2026 | One support ticket as JSON, with the customer's messages. |
| ticket 2144 | One support ticket as JSON, with the customer's messages. |
| ticket 2125 | One support ticket as JSON, with the customer's messages. |
| ticket 2295 | One support ticket as JSON, with the customer's messages. |
| ticket 2273 | One support ticket as JSON, with the customer's messages. |
| ticket 2221 | One support ticket as JSON, with the customer's messages. |
| ticket 2148 | One support ticket as JSON, with the customer's messages. |
| ticket 2107 | One support ticket as JSON, with the customer's messages. |
| ticket 2311 | One support ticket as JSON, with the customer's messages. |
| ticket 2327 | One support ticket as JSON, with the customer's messages. |
| ticket 2180 | One support ticket as JSON, with the customer's messages. |
| ticket 2051 | One support ticket as JSON, with the customer's messages. |
| ticket 2284 | One support ticket as JSON, with the customer's messages. |
| ticket 2025 | One support ticket as JSON, with the customer's messages. |
| ticket 2308 | One support ticket as JSON, with the customer's messages. |
| ticket 2216 | One support ticket as JSON, with the customer's messages. |
| ticket 2326 | One support ticket as JSON, with the customer's messages. |
| ticket 2071 | One support ticket as JSON, with the customer's messages. |
| ticket 2296 | One support ticket as JSON, with the customer's messages. |
| ticket 2119 | One support ticket as JSON, with the customer's messages. |
| ticket 2118 | One support ticket as JSON, with the customer's messages. |
| ticket 2145 | One support ticket as JSON, with the customer's messages. |
| ticket 2086 | One support ticket as JSON, with the customer's messages. |
| ticket 2160 | One support ticket as JSON, with the customer's messages. |
| ticket 2280 | One support ticket as JSON, with the customer's messages. |
| ticket 2277 | One support ticket as JSON, with the customer's messages. |
| ticket 2200 | One support ticket as JSON, with the customer's messages. |
| ticket 2043 | One support ticket as JSON, with the customer's messages. |
| ticket 2266 | One support ticket as JSON, with the customer's messages. |
| ticket 2208 | One support ticket as JSON, with the customer's messages. |
| ticket 2096 | One support ticket as JSON, with the customer's messages. |
| ticket 2024 | One support ticket as JSON, with the customer's messages. |
| ticket 2065 | One support ticket as JSON, with the customer's messages. |
| ticket 2183 | One support ticket as JSON, with the customer's messages. |
| ticket 2052 | One support ticket as JSON, with the customer's messages. |
| ticket 2302 | One support ticket as JSON, with the customer's messages. |
| ticket 2255 | One support ticket as JSON, with the customer's messages. |
| ticket 2210 | One support ticket as JSON, with the customer's messages. |
| ticket 2168 | One support ticket as JSON, with the customer's messages. |
| ticket 2192 | One support ticket as JSON, with the customer's messages. |
| ticket 2252 | One support ticket as JSON, with the customer's messages. |
| ticket 2089 | One support ticket as JSON, with the customer's messages. |
| ticket 2269 | One support ticket as JSON, with the customer's messages. |
| ticket 2094 | One support ticket as JSON, with the customer's messages. |
| ticket 2042 | One support ticket as JSON, with the customer's messages. |
| ticket 2323 | One support ticket as JSON, with the customer's messages. |
| ticket 2098 | One support ticket as JSON, with the customer's messages. |
| ticket 2314 | One support ticket as JSON, with the customer's messages. |
| ticket 2197 | One support ticket as JSON, with the customer's messages. |
| ticket 2068 | One support ticket as JSON, with the customer's messages. |
| ticket 2195 | One support ticket as JSON, with the customer's messages. |
| ticket 2159 | One support ticket as JSON, with the customer's messages. |
| ticket 2073 | One support ticket as JSON, with the customer's messages. |
| ticket 2003 | One support ticket as JSON, with the customer's messages. |
| ticket 2297 | One support ticket as JSON, with the customer's messages. |
| ticket 2116 | One support ticket as JSON, with the customer's messages. |
| ticket 2031 | One support ticket as JSON, with the customer's messages. |
| ticket 2211 | One support ticket as JSON, with the customer's messages. |
| ticket 2287 | One support ticket as JSON, with the customer's messages. |
| ticket 2050 | One support ticket as JSON, with the customer's messages. |
| ticket 2103 | One support ticket as JSON, with the customer's messages. |
| ticket 2097 | One support ticket as JSON, with the customer's messages. |
| ticket 2070 | One support ticket as JSON, with the customer's messages. |
| ticket 2313 | One support ticket as JSON, with the customer's messages. |
| ticket 2288 | One support ticket as JSON, with the customer's messages. |
| ticket 2032 | One support ticket as JSON, with the customer's messages. |
| ticket 2028 | One support ticket as JSON, with the customer's messages. |
| ticket 2293 | One support ticket as JSON, with the customer's messages. |
| ticket 2127 | One support ticket as JSON, with the customer's messages. |
| ticket 2100 | One support ticket as JSON, with the customer's messages. |
| ticket 2120 | One support ticket as JSON, with the customer's messages. |
| ticket 2152 | One support ticket as JSON, with the customer's messages. |
| ticket 2080 | One support ticket as JSON, with the customer's messages. |
| ticket 2194 | One support ticket as JSON, with the customer's messages. |
| ticket 2141 | One support ticket as JSON, with the customer's messages. |
| ticket 2212 | One support ticket as JSON, with the customer's messages. |
| ticket 2175 | One support ticket as JSON, with the customer's messages. |
| ticket 2214 | One support ticket as JSON, with the customer's messages. |
| ticket 2272 | One support ticket as JSON, with the customer's messages. |
| ticket 2000 | One support ticket as JSON, with the customer's messages. |
| ticket 2264 | One support ticket as JSON, with the customer's messages. |
| ticket 2232 | One support ticket as JSON, with the customer's messages. |
| ticket 2186 | One support ticket as JSON, with the customer's messages. |
| ticket 2087 | One support ticket as JSON, with the customer's messages. |
| ticket 2219 | One support ticket as JSON, with the customer's messages. |
| ticket 2299 | One support ticket as JSON, with the customer's messages. |
| ticket 2223 | One support ticket as JSON, with the customer's messages. |
| ticket 2164 | One support ticket as JSON, with the customer's messages. |
| ticket 2301 | One support ticket as JSON, with the customer's messages. |
| ticket 2309 | One support ticket as JSON, with the customer's messages. |
| ticket 2315 | One support ticket as JSON, with the customer's messages. |
| ticket 2134 | One support ticket as JSON, with the customer's messages. |
| ticket 2161 | One support ticket as JSON, with the customer's messages. |
| ticket 2038 | One support ticket as JSON, with the customer's messages. |
| ticket 2278 | One support ticket as JSON, with the customer's messages. |
| ticket 2248 | One support ticket as JSON, with the customer's messages. |
| ticket 2033 | One support ticket as JSON, with the customer's messages. |
| ticket 2131 | One support ticket as JSON, with the customer's messages. |
| ticket 2048 | One support ticket as JSON, with the customer's messages. |
| ticket 2064 | One support ticket as JSON, with the customer's messages. |
| ticket 2283 | One support ticket as JSON, with the customer's messages. |
| ticket 2234 | One support ticket as JSON, with the customer's messages. |
| ticket 2318 | One support ticket as JSON, with the customer's messages. |
| ticket 2306 | One support ticket as JSON, with the customer's messages. |
| ticket 2307 | One support ticket as JSON, with the customer's messages. |
| ticket 2205 | One support ticket as JSON, with the customer's messages. |
| ticket 2259 | One support ticket as JSON, with the customer's messages. |
| ticket 2029 | One support ticket as JSON, with the customer's messages. |
| ticket 2316 | One support ticket as JSON, with the customer's messages. |
| ticket 2014 | One support ticket as JSON, with the customer's messages. |
| ticket 2185 | One support ticket as JSON, with the customer's messages. |
| ticket 2162 | One support ticket as JSON, with the customer's messages. |
| ticket 2156 | One support ticket as JSON, with the customer's messages. |
| ticket 2222 | One support ticket as JSON, with the customer's messages. |
| ticket 2041 | One support ticket as JSON, with the customer's messages. |
| ticket 2202 | One support ticket as JSON, with the customer's messages. |
| ticket 2016 | One support ticket as JSON, with the customer's messages. |
| ticket 2083 | One support ticket as JSON, with the customer's messages. |
| ticket 2169 | One support ticket as JSON, with the customer's messages. |
| ticket 2201 | One support ticket as JSON, with the customer's messages. |
| ticket 2199 | One support ticket as JSON, with the customer's messages. |
| ticket 2249 | One support ticket as JSON, with the customer's messages. |
| ticket 2109 | One support ticket as JSON, with the customer's messages. |
| ticket 2020 | One support ticket as JSON, with the customer's messages. |
| ticket 2139 | One support ticket as JSON, with the customer's messages. |
| ticket 2143 | One support ticket as JSON, with the customer's messages. |
| ticket 2187 | One support ticket as JSON, with the customer's messages. |
| ticket 2157 | One support ticket as JSON, with the customer's messages. |
| ticket 2022 | One support ticket as JSON, with the customer's messages. |
| ticket 2182 | One support ticket as JSON, with the customer's messages. |
| ticket 2267 | One support ticket as JSON, with the customer's messages. |
| ticket 2158 | One support ticket as JSON, with the customer's messages. |
| ticket 2196 | One support ticket as JSON, with the customer's messages. |
| ticket 2231 | One support ticket as JSON, with the customer's messages. |
| ticket 2102 | One support ticket as JSON, with the customer's messages. |
| ticket 2067 | One support ticket as JSON, with the customer's messages. |
| ticket 2072 | One support ticket as JSON, with the customer's messages. |
| ticket 2122 | One support ticket as JSON, with the customer's messages. |
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct resource and action: search vs. get for tickets, get for customers, export, note addition, and refund. Boundaries are clear, and the ticket lookup pair is well differentiated (bulk search vs. single-ticket detail).
Naming Consistency5/5
All names follow a consistent verb_noun snake_case pattern (search_tickets, get_ticket, get_customer, export_tickets, add_internal_note, issue_refund). No mixed conventions or vague verbs.
Tool Count5/5
Six tools is well-scoped for a helpdesk surface, with each tool clearly earning its place. No redundancy or thin coverage.
Completeness3/5
Read and write operations cover lookup, export, notes, and refunds, but there is no ticket creation, status update/close, or customer-facing reply, which are core helpdesk lifecycle actions. These gaps will limit end-to-end agent workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues