servicedesk-plus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SDP_API_KEY | Yes | Your technician key/authtoken from ServiceDesk Plus profile page. | |
| SDP_BASE_URL | Yes | The base URL of your ServiceDesk Plus instance (e.g., productsupport.example.com). | |
| SDP_USERNAME | Yes | Your username/email for ServiceDesk Plus. |
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_ticketsA | Retrieve, search, and filter ServiceDesk Plus tickets. Args: status: Optional status filter (e.g. 'Open', 'In Progress', 'Closed'). requester_email: Optional requester email address filter. search_query: Optional text keyword search for ticket subjects. row_count: Number of tickets to retrieve (default: 20, max: 100). start_index: 1-based start index for paginated results (default: 1). |
| get_ticketA | Retrieve detailed information on a single ticket, including its status, resolution, and description. Args: ticket_id: The unique numeric ID of the ticket to retrieve. |
| create_ticketA | Create a new Help Desk ticket in ServiceDesk Plus. Args: subject: Short summary or subject of the ticket. description: Full plain-text or HTML description detailing the issue. priority: Optional priority name (e.g. 'High', 'Medium', 'Low'). requester_email: Optional email of the requester. If omitted, uses default. |
| update_ticketA | Update fields on an existing ticket in ServiceDesk Plus. Args: ticket_id: The unique numeric ID of the ticket to update. subject: Optional new subject for the ticket. description: Optional new plain-text or HTML description. status: Optional new status name (e.g. 'Open', 'In Progress', 'Closed'). |
| add_ticket_noteA | Append a technical update or administrative note to a ticket. Args: ticket_id: The unique numeric ID of the ticket. note: Text content of the note to append. |
| list_ticket_notesA | List all notes attached to a specific ticket. Args: ticket_id: The unique numeric ID of the ticket. |
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 has a distinct purpose: list, detail, create, update, add note, and list notes. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_tickets, create_ticket, update_ticket). This is uniform and predictable.
Six tools is well-scoped for a help desk ticket server, covering core ticket operations and note management without unnecessary bloat.
The tool set covers create, read, update, list, and notes. Missing delete is acceptable for tickets, but lack of assign/transfer or note editing is a minor gap.