Skip to main content
Glama

ninja_list_ticket_statuses

Retrieve all configured ticket statuses to streamline workflow management in NinjaOne. Use this tool to get a complete list of statuses for filtering or automation.

Instructions

List all available ticket statuses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the ninja_list_ticket_statuses tool. It makes a GET request to '/ticketing/statuses' endpoint via the NinjaOneClient.
      handler: async (_args, client: NinjaOneClient) => client.get('/ticketing/statuses'),
    },
  • The input schema for ninja_list_ticket_statuses - an empty object with no required parameters.
    inputSchema: { type: 'object', properties: {} },
  • The tool definition for ninja_list_ticket_statuses registered within the ticketingTools array. It is exported and later aggregated into ALL_TOOLS in src/tools/index.ts.
    {
      tool: {
        name: 'ninja_list_ticket_statuses',
        description: 'List all available ticket statuses.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/ticketing/statuses'),
    },
    {
      tool: {
        name: 'ninja_list_ticket_forms',
        description: 'List all available ticket forms.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/ticketing/ticket-form'),
    },
  • The ALL_TOOLS array aggregates all tool definitions including ticketingTools (which contains ninja_list_ticket_statuses) for registration with the MCP server.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • src/index.ts:31-32 (registration)
    The MCP server's ListToolsRequestSchema handler registers all tools (including ninja_list_ticket_statuses) by returning their metadata.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: ALL_TOOLS.map((def) => def.tool),
Behavior3/5

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

Without annotations, the description must disclose behavior. It implies a read-only operation, but lacks details on authentication, rate limits, or potential side effects. For a simple listing tool, this is adequate but not thorough.

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, front-loaded sentence with no unnecessary words. It is perfectly concise for the tool's simplicity.

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 no parameters and no output schema, the description is nearly complete. However, it could mention how the status list might be used with other ticket tools, but this is optional for such a simple tool.

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

Parameters4/5

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

There are no parameters, so schema coverage is 100%. The description adds value by clarifying that the tool lists all statuses, which goes beyond the empty schema.

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 tool lists ticket statuses. The verb 'list' and resource 'ticket statuses' are specific, and it distinguishes from sibling tools like 'ninja_get_ticket' by focusing on statuses rather than individual tickets.

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. While the tool is simple, there is no mention of prerequisites or context for its use.

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