Skip to main content
Glama
wtf-amnn

customer-support-mcp

by wtf-amnn

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_customer_toolA

Create a new customer record.

Args:
    name: Full name of the customer.
    email: Customer's email address (must be unique).
    phone: Optional phone number.
get_customer_toolA

Fetch a customer by their id.

Args:
    customer_id: The customer's numeric id.
get_ticket_details_toolA

Get full context for a ticket: details, customer info, and all comments.

Use this instead of get_ticket_tool when you need the complete picture,
including the customer and the comment history.

Args:
    ticket_id: The ticket's numeric id.
get_knowledge_articles_toolA

Read support knowledge-base articles for a category.

Use this to find relevant policy or troubleshooting guidance before
advising on a ticket.

Args:
    category: One of 'billing' or 'account'.
list_customers_toolA

List customers, optionally filtered by status.

Args:
    status: Filter by 'active' or 'inactive'. Omit for all customers.
    limit: Maximum number of customers to return.
create_ticket_toolB

Create a support ticket for an existing customer.

Args:
    customer_id: Id of the customer raising the ticket.
    subject: Short summary of the issue.
    description: Full description of the issue.
    priority: One of 'low', 'medium', 'high', 'urgent'.
list_tickets_toolA

List tickets with optional filters. Use this to find tickets matching criteria.

Args:
    status: Filter by 'open', 'in_progress', 'resolved', or 'closed'. Omit for all.
    priority: Filter by 'low', 'medium', 'high', or 'urgent'. Omit for all.
    customer_id: Only tickets belonging to this customer.
    limit: Maximum number of tickets to return.
get_ticket_toolC

Fetch a single ticket by id.

Args:
    ticket_id: The ticket's numeric id.
assign_ticket_toolC

Assign a ticket to a support team.

Args:
    ticket_id: The ticket to assign.
    team: Name of the team, e.g. 'billing_team' or 'security_team'.
add_comment_toolC

Add a comment to a ticket.

Args:
    ticket_id: The ticket to comment on.
    author: Who is writing the comment.
    body: The comment text.
change_ticket_status_toolA

Change a ticket's status. Only valid transitions are allowed.

Valid transitions: open -> in_progress/closed; in_progress -> resolved/open/closed;
resolved -> closed/in_progress; closed is terminal.

Args:
    ticket_id: The ticket to update.
    new_status: One of 'open', 'in_progress', 'resolved', 'closed'.
resolve_ticket_toolC

Mark a ticket as resolved.

Args:
    ticket_id: The ticket to resolve.
delete_ticket_toolA

Permanently delete a ticket and all its comments. Destructive and irreversible.

Args:
    ticket_id: The ticket to delete.
    confirm: Must be explicitly set to true to proceed with deletion.

Prompts

Interactive templates invoked by user choice

NameDescription
triage_ticketTriage a support ticket: assess, categorize, and recommend next steps. Args: ticket_id: The ticket to triage.
daily_queue_reviewReview the open ticket queue and produce a prioritized action list.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 13 tools

Disambiguation4/5

Most tools are distinct, but get_ticket_tool and get_ticket_details_tool overlap, as do resolve_ticket_tool and change_ticket_status_tool. The descriptions provide clear guidance on when to use each, so an agent can disambiguate, though slight redundancy exists.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, e.g., get_customer_tool, list_tickets_tool, change_ticket_status_tool. No mixed conventions or irregular verbs.

Tool Count5/5

With 13 tools covering customers, tickets, comments, assignments, and knowledge articles, the count is well-scoped for a customer support server. Each tool serves a clear purpose without excessive redundancy.

Completeness4/5

The surface covers core customer and ticket lifecycles: create/get/list for customers, full ticket management (create, list, get, status changes, resolve, assign, comment, delete). Minor gaps include no update/delete for customers and no ability to modify ticket content, but these are not critical for typical support workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues