Skip to main content
Glama

ninja_list_groups

Retrieve all device groups in NinjaOne to view, filter, and manage your organized device collections.

Instructions

List all device groups in NinjaOne.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'ninja_list_groups' that calls client.get('/groups') to list all device groups.
    handler: async (_args, client: NinjaOneClient) => client.get('/groups'),
  • The input schema definition for 'ninja_list_groups' - an empty object (no parameters required).
    inputSchema: { type: 'object', properties: {} },
  • Registration of 'ninja_list_groups' as part of the systemTools array with name, description, inputSchema, and handler.
    export const systemTools: ToolDef[] = [
      {
        tool: {
          name: 'ninja_list_groups',
          description: 'List all device groups in NinjaOne.',
          inputSchema: { type: 'object', properties: {} },
        },
        handler: async (_args, client: NinjaOneClient) => client.get('/groups'),
      },
  • ALL_TOOLS aggregation that includes systemTools (containing ninja_list_groups) into the full tool list.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • The NinjaOneClient.get() helper method used by the handler to make the authenticated GET request to '/groups'.
    async get<T = unknown>(path: string, params?: Record<string, unknown>): Promise<T> {
      try {
        const res = await this.http.get<T>(path, {
          params,
          headers: await this.authHeader(),
        });
        return res.data;
      } catch (err) {
        throw new Error(`GET ${path} failed: ${apiError(err)}`);
      }
    }
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as pagination, rate limits, or what 'groups' encompasses. For a list operation, minimal behavioral context is given.

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?

One short sentence with no fluff. Concise and directly conveys the tool's purpose.

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, no output schema, and a simple purpose, the description is nearly complete. However, it could mention if results are paginated or if there are any filtering options.

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?

The input schema has zero parameters, so the description does not need to explain parameter meanings. Baseline of 4 for no parameters 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?

The description states 'List all device groups in NinjaOne' with a clear verb (list) and resource (device groups). Among siblings with many list tools for different entities, this distinguishes itself by specifying 'groups'.

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 versus alternatives like ninja_get_group_device_ids. No exclusions or context provided.

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