Skip to main content
Glama

ninja_list_ticketing_users

Retrieve all app users and contacts available in the ticketing system for user management or ticket assignment.

Instructions

List all app users and contacts available in the ticketing system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'ninja_list_ticketing_users' tool logic. It makes a GET request to '/ticketing/app-user-contact' to list all app users and contacts.
    handler: async (_args, client: NinjaOneClient) =>
      client.get('/ticketing/app-user-contact'),
  • The tool definition including name, description, and input schema. The tool takes no parameters (empty object schema).
    tool: {
      name: 'ninja_list_ticketing_users',
      description: 'List all app users and contacts available in the ticketing system.',
      inputSchema: { type: 'object', properties: {} },
  • The tool is registered via ALL_TOOLS array which spreads ticketingTools. This array is used to build the tool map and list tools in the MCP server.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
  • src/index.ts:24-24 (registration)
    The MCP server maps tool names to handlers and registers tools via ListToolsRequestSchema and CallToolRequestSchema.
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
  • The ToolDef interface that defines the shape of each tool definition, including the tool metadata and handler function.
    export interface ToolDef {
      tool: Tool;
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      handler: (args: any, client: NinjaOneClient) => Promise<unknown>;
    }
Behavior2/5

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

With no annotations, the description carries full burden but only says 'list all.' It does not disclose pagination, permissions, rate limits, or whether the list includes details like IDs or names.

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 sentence with no wasted words. It is front-loaded and efficient.

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?

For a simple no-parameter tool, the description is adequate but lacks details about the return format or pagination. It could be more complete by specifying what fields are returned.

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 the description does not need to add parameter info. It clarifies that the tool lists both app users and contacts, which is appropriate for a zero-parameter tool.

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 'list' and resource 'app users and contacts available in the ticketing system.' It distinguishes from sibling tools like ninja_list_users and ninja_list_contacts by specifying the ticketing context, but 'app users' is slightly ambiguous.

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 like ninja_list_users or ninja_list_contacts. The description does not explain the difference or mention the ticketing-specific scope.

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