POS Support MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POS_SUPPORT_DB_PATH | No | Path to the SQLite database file used by the server. Override to use an isolated database. | data/pos_support.db |
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 |
|---|---|
| list_branchesA | List fictitious branches, optionally filtered by status. |
| get_branchA | Get one branch by its stable business code. |
| list_terminalsB | List terminals, optionally filtered by branch and status. |
| get_terminalB | Get one terminal by branch code and branch-local terminal code. |
| list_incidentsB | List incidents using optional branch, terminal, status, and priority filters. |
| get_incidentB | Get an incident with its branch, optional terminal, and ordered history. |
| search_similar_incidentsB | Find incidents using deterministic local Jaccard text similarity. |
| create_incidentB | Create an open branch-wide or terminal-specific support incident. |
| update_incidentB | Edit an active incident or move it from open to in_progress. |
| resolve_incidentC | Resolve an active incident with a required applied solution. |
| get_critical_incidentsA | List unresolved critical incidents, optionally for one branch. |
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 11 tools
Most tools are clearly distinct: get_* for single resources, list_* for collections, and create/update/resolve for incident lifecycle. The main overlap is get_critical_incidents, which largely duplicates list_incidents with status and priority filters, though it may serve as a convenience shortcut.
Tool names generally follow a verb_noun pattern with singular get_ and plural list_ prefixes, and create/update/resolve are consistent. The slight inconsistency is get_critical_incidents returning a list rather than using list_, but the naming remains readable and predictable.
Eleven tools is well-scoped for a POS support domain, covering branch/terminal lookup, incident management, and incident search. Each tool has a clear role, and the count feels appropriate without unnecessary bloat.
The incident lifecycle is well covered with create, update, resolve, and detailed retrieval, and branch/terminal context is supported. Minor gaps exist such as no explicit cancel/reopen operation or dedicated comment/note endpoint, but agents can handle most support workflows.