MCP Request Tracker CrunchTools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RT_URL | Yes | Base URL of your RT server | |
| RT_PASS | Yes | RT password | |
| RT_USER | Yes | RT username | |
| RT_HTTP_PASS | No | HTTP Basic Auth password | |
| RT_HTTP_USER | No | HTTP Basic Auth username |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tickets_toolC | Search for tickets using RT query syntax. |
| get_ticket_toolC | Get details of a specific ticket. |
| get_ticket_history_toolB | Get the history/changelog of a ticket. |
| get_my_open_tickets_toolB | Get all open tickets assigned to a user. |
| get_new_tickets_toolB | Get all new (unassigned) tickets, optionally filtered by queue. |
| set_ticket_owner_toolC | Set the owner of a ticket (take/assign ticket). |
| set_ticket_status_toolC | Set the status of a ticket. |
| update_ticket_toolC | Update ticket fields (subject, priority, queue). All fields are optional. |
| resolve_ticket_toolB | Resolve/close a ticket, optionally adding a comment. |
| open_ticket_toolB | Open a ticket (change status from new to open), optionally taking ownership. |
| take_ticket_toolC | Take ownership of a ticket and open it. |
| set_time_worked_toolC | Set the total time worked on a ticket. |
| add_time_worked_toolC | Add time to the time worked on a ticket. |
| add_ticket_comment_toolA | Add a private comment/note to a ticket (not visible to requestor). |
| reply_to_ticket_toolA | Reply to a ticket (correspondence visible to requestor). |
| create_ticket_toolC | Create a new ticket. |
| complete_weekly_checklist_toolA | Complete a weekly checklist ticket with results. This is a workflow shortcut that:
|
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 17 tools
Tools are mostly distinct, but there is overlap among set_ticket_owner_tool, take_ticket_tool, and open_ticket_tool, which all can set ownership or change status. complete_weekly_checklist_tool also duplicates a multi-step workflow, though its description clearly marks it as a shortcut. An agent may struggle to choose between the ownership/open variants.
All tools use snake_case with a consistent _tool suffix and follow a verb_noun pattern (e.g., get_ticket_tool, set_ticket_status_tool). This is highly predictable and uniform throughout.
17 tools is slightly above the typical 3-15 range but remains reasonable for a full ticket-tracking workflow with specialized actions. A few tools could be consolidated, but each generally has a clear role.
The surface covers the full ticket lifecycle: create, search, get, update, assign, status changes, comments (private/public), time tracking, history, and resolution. No major gaps for typical RT workflows.