Skip to main content
Glama

get_ticket

Retrieve detailed support ticket information from FitSlot by providing the ticket ID to access specific case details and status updates.

Instructions

Get detailed information about a specific ticket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIdYes

Implementation Reference

  • MCP tool definition for 'get_ticket' including description, input schema (Zod), and execute handler that validates ticketId, fetches ticket via apiService.getTicket, formats response as JSON text content.
    get_ticket: {
      description: 'Get detailed information about a specific ticket',
      parameters: z.object({
        ticketId: z.string().describe('ID of the ticket to retrieve')
      }),
      execute: async (args: { ticketId: string }) => {
        try {
          logger.info('Getting ticket details', args);
    
          validateNotEmpty(args.ticketId, 'Ticket ID');
    
          const ticket = await apiService.getTicket(args.ticketId);
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(
                  {
                    success: true,
                    ticket
                  },
                  null,
                  2
                )
              }
            ]
          };
        } catch (error) {
          logger.error('Failed to get ticket', error);
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(
                  {
                    success: false,
                    error: error instanceof Error ? error.message : 'Unknown error'
                  },
                  null,
                  2
                )
              }
            ],
            isError: true
          };
        }
      }
    },
  • src/index.ts:60-68 (registration)
    Registers ticket tools (including get_ticket) by calling createTicketTools and merging into allTools object used in MCP server's listTools and callTool request handlers.
    const ticketTools = createTicketTools(apiService);
    const chatbotTools = createChatbotTools(chatbotService);
    const pdfTools = createPDFTools(pdfService);
    
    const allTools = {
      ...ticketTools,
      ...chatbotTools,
      ...pdfTools
    };
  • Helper method in FitSlotAPIService that performs the actual HTTP GET request to retrieve ticket details from the FitSlot API endpoint `/api/tickets/${ticketId}`.
    async getTicket(ticketId: string): Promise<Ticket> {
      try {
        const response = await this.client.get<Ticket>(`/api/tickets/${ticketId}`);
        logger.info('Ticket retrieved', { ticketId });
        return response.data;
      } catch (error) {
        logger.error('Failed to get ticket', error);
        throw error;
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a read-only operation ('Get') but doesn't confirm safety aspects like whether it's idempotent, requires authentication, has rate limits, or what happens with invalid IDs. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly. Every word earns its place.

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 the complexity (a read operation with 1 parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral traits, error handling, return format, or usage context. For a tool in a set with multiple ticket-related siblings, more guidance is needed to be fully helpful.

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 0%, so the schema provides no parameter descriptions. The description adds minimal value by implying a 'ticketId' parameter is needed ('about a specific ticket'), but doesn't explain format, constraints, or examples. With 1 parameter and low coverage, it partially compensates but remains vague.

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 verb ('Get') and resource ('detailed information about a specific ticket'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_tickets' (which likely returns multiple tickets) or 'create_ticket'/'update_ticket' (which are write operations), missing full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a ticket ID), contrast with 'list_tickets' for bulk retrieval, or specify use cases like viewing ticket details after creation. This leaves the agent without contextual usage cues.

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/osmarsant/fitslot-mcp'

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