Skip to main content
Glama

ninja_get_ticket_form

Get details of a ticket form and its fields by providing the ticket form ID.

Instructions

Get details of a specific ticket form including its fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTicket form ID

Implementation Reference

  • The handler function for 'ninja_get_ticket_form' that destructures 'id' from args and makes a GET request to /ticketing/ticket-form/{id} via the NinjaOneClient.
      handler: async ({ id }, client: NinjaOneClient) =>
        client.get(`/ticketing/ticket-form/${id}`),
    },
  • The input schema for 'ninja_get_ticket_form' requiring an 'id' (number) property.
    inputSchema: {
      type: 'object',
      required: ['id'],
      properties: {
        id: { type: 'number', description: 'Ticket form ID' },
      },
    },
  • The tool definition registration entry within the ticketingTools array, defining the tool name, description, inputSchema, and handler.
    {
      tool: {
        name: 'ninja_get_ticket_form',
        description: 'Get details of a specific ticket form including its fields.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Ticket form ID' },
          },
        },
      },
      handler: async ({ id }, client: NinjaOneClient) =>
        client.get(`/ticketing/ticket-form/${id}`),
    },
  • The ticketingTools array is spread into ALL_TOOLS, which is the central registration of all tools including 'ninja_get_ticket_form'.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • The ToolDef interface defining the shape of a tool definition, including the 'tool' (name, description, inputSchema) and 'handler' function.
    export interface ToolDef {
      tool: Tool;
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      handler: (args: any, client: NinjaOneClient) => Promise<unknown>;
    }
Behavior3/5

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

No annotations provided, so description carries full burden. States it is a read operation ('get details'), but does not disclose potential rate limits, authorization needs, or what other details beyond fields are returned. Adequate but not rich.

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 11 words, no fluff. Verb and resource are front-loaded. Every word earns its place.

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

Completeness4/5

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

Given low complexity (1 param, no output schema), the description covers the core purpose and highlights fields. Could be more detailed about return structure, but acceptable for a simple retrieval tool.

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 coverage is 100% with one parameter (id). The description adds minimal value beyond schema, only mentioning 'including its fields' which implies return content, not parameter semantics. Baseline 3 is appropriate.

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 verb 'Get', resource 'ticket form', and scope 'including its fields'. Distinguishes from sibling tools like ninja_list_ticket_forms (list all) and ninja_get_ticket (get ticket, not form).

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 vs alternatives. Does not mention when to prefer this over ninja_get_ticket or ninja_list_ticket_forms. Missing context about prerequisites.

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/Allied-Business-Solutions/ninjaone-mcp'

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