Skip to main content
Glama

assign_ticket

Idempotent

Assign an ITSM ticket to a specific user by providing ticket ID and user ID, with support for multiple systems including ServiceNow, Jira, Zendesk, Ivanti Neurons, and Cherwell.

Instructions

Assign a ticket to a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYesID of the ticket to assign
user_idYesUsername or ID of the user to assign to
systemNoITSM system to usejira

Implementation Reference

  • Core handler function for assign_ticket: looks up the ticket by ID, assigns it to the given user_id, updates the timestamp, and returns the result.
    function assignTicket({ ticket_id, user_id }) {
      const ticket = tickets.get(ticket_id);
      if (!ticket) return { success: false, error: `Ticket ${ticket_id} not found` };
      ticket.assignee = user_id;
      ticket.updated_at = new Date().toISOString();
      tickets.set(ticket_id, ticket);
      return { success: true, ticket: { id: ticket.id, title: ticket.title, assignee: user_id, system: ticket.system } };
    }
  • index.js:269-288 (registration)
    MCP server.tool registration for 'assign_ticket' with Zod schema validation for ticket_id and user_id parameters, annotations, and the async handler that delegates to the assignTicket function.
    server.tool(
      'assign_ticket',
      'Assign a ticket to a specific user',
      {
        ticket_id: z.string().describe('ID of the ticket to assign'),
        user_id: z.string().describe('Username or ID of the user to assign to'),
        system: systemSchema.optional(),
      },
      {
        title: 'Assign Ticket',
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
      async ({ ticket_id, user_id }) => {
        const result = assignTicket({ ticket_id, user_id });
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • Zod schema defining the input parameters for assign_ticket: ticket_id (string), user_id (string), and optional system (enum).
    ticket_id: z.string().describe('ID of the ticket to assign'),
    user_id: z.string().describe('Username or ID of the user to assign to'),
    system: systemSchema.optional(),
  • Frontend MCPService helper that wraps the assign_ticket tool call for use in the browser/client application.
    async assignTicket(ticketId, userId, system = null) {
      return this.callTool('assign_ticket', {
        ticket_id: ticketId,
        user_id: userId,
        ...(system && { system }),
      });
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate non-readOnly, non-destructive, idempotent. Description adds 'assign' but no further behavioral details (e.g., reassignment effects, notifications). Minimal additional value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words, front-loads the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple assign action, but lacks usage guidance and return value indication. With annotations present, no major gaps but not rich.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters with descriptions (100% coverage). Description does not add extra meaning beyond summarizing the action.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action ('assign'), the resource ('a ticket'), and the target ('to a specific user'). Distinguishes from sibling tools like create_ticket, get_ticket, update_ticket.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no prerequisites mentioned (e.g., ticket existence, user permissions), and no when-not-to-use context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/madosh/MCP-ITSM'

If you have feedback or need assistance with the MCP directory API, please join our Discord server