support-tools
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 |
|---|---|
| get_customerB | Customer profile: verification status, VIP tier, balance, active bonus. |
| get_transactionsA | Most recent deposits and withdrawals of a customer, newest first. |
| search_knowledgeA | Search the support knowledge base. Returns ranked sections with a score; state policies only from these. |
| create_ticketA | Escalate to a human agent. Use only on explicit request or when the tools cannot answer. Returns the ticket. |
| list_ticketsC | Tickets created in this session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage | System prompt for a support agent that uses these tools correctly. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs | Knowledge-base documents (id, title, category). |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: customer profile, transaction history, knowledge lookup, ticket listing, and ticket creation. There is no meaningful overlap between them, so an agent can reliably choose the right tool.
All tools use a consistent snake_case verb_noun convention: get_customer, get_transactions, search_knowledge, list_tickets, create_ticket. The naming is uniform and predictable.
Five tools is an appropriate size for a focused customer-support toolset. It covers the core operations without unnecessary redundancy or missing essentials.
The set covers the main support workflow: retrieve customer info, view transactions, search knowledge, and escalate by creating a ticket. There are no obvious dead ends for the server's stated support purpose.