Skip to main content
Glama

get_ticket

Retrieve specific ticket details by ID using the MCP server mcptix, enabling efficient ticket management and task tracking for AI assistants.

Instructions

Get a ticket by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTicket ID

Implementation Reference

  • The handler function that executes the get_ticket tool logic: validates the ticket ID, fetches the ticket using TicketQueries.getTicketById, and returns it wrapped in a success response.
    export function handleGetTicket(ticketQueries: TicketQueries, args: any): ToolResponse {
      if (!args.id) {
        Logger.warn('McpServer', 'Ticket ID is required');
        throw new Error('Ticket ID is required');
      }
    
      Logger.debug('McpServer', `Getting ticket with ID: ${args.id}`);
    
      const ticket = ticketQueries.getTicketById(args.id);
    
      if (!ticket) {
        Logger.warn('McpServer', `Ticket with ID ${args.id} not found`);
        throw new Error(`Ticket with ID ${args.id} not found`);
      }
    
      Logger.debug('McpServer', `Found ticket: ${args.id}`);
    
      return createSuccessResponse(ticket);
    }
  • The JSON schema definition for the get_ticket tool, specifying the required 'id' parameter.
      name: 'get_ticket',
      description: 'Get a ticket by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Ticket ID',
          },
        },
        required: ['id'],
      },
    },
  • The registration of the get_ticket tool in the MCP CallToolRequestSchema handler switch statement, dispatching to the handleGetTicket function.
    case 'get_ticket':
      return handleGetTicket(ticketQueries, args);
Behavior2/5

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

No annotations are provided, so the description carries full burden but adds minimal behavioral context. It states 'Get' which implies a read operation, but doesn't disclose traits like whether it requires authentication, returns full or partial data, handles errors, or has rate limits. This is inadequate for a tool with zero annotation coverage.

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?

The description is extremely concise ('Get a ticket by ID'), front-loaded with the core action, and wastes no words. Every part of the sentence is essential, making it efficient and easy to parse, though it may be overly brief for completeness.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple parameter, the description is incomplete. It doesn't explain what the tool returns (e.g., ticket details, status), error conditions, or behavioral aspects. For a basic read tool, this leaves significant gaps in understanding its full context and usage.

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 description coverage is 100%, with the parameter 'id' documented as 'Ticket ID' in the schema. The description adds no additional meaning beyond this, such as format examples (e.g., numeric vs. string) or constraints. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is provided.

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

Purpose4/5

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

The description clearly states the action ('Get') and resource ('a ticket by ID'), making the purpose understandable. It distinguishes from siblings like list_tickets (multiple tickets) and search_tickets (filtered search), though not explicitly. However, it lacks specificity about what 'get' entails (e.g., retrieve details vs. status), preventing a perfect score.

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 is provided on when to use this tool versus alternatives. For example, it doesn't clarify that this is for retrieving a single known ticket ID, whereas list_tickets returns multiple tickets or search_tickets filters by criteria. The description implies usage by mentioning 'by ID' but offers no explicit context or exclusions.

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

Related 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/ownlytics/mcptix'

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