Skip to main content
Glama

ninja_list_node_roles

Retrieve a complete list of all available device or node roles in your NinjaOne environment.

Instructions

List all available device/node roles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the tool - makes a GET request to /roles endpoint via NinjaOneClient
      handler: async (_args, client: NinjaOneClient) => client.get('/roles'),
    },
  • Tool definition including inputSchema (empty object, no params) and the handler
    {
      tool: {
        name: 'ninja_list_node_roles',
        description: 'List all available device/node roles.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/roles'),
    },
  • Tool registration - policyTools (containing ninja_list_node_roles) is spread into ALL_TOOLS array
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • src/index.ts:31-33 (registration)
    MCP server registration - tool is listed via ListToolsRequestSchema and dispatched via CallToolRequestSchema using a handler map built from ALL_TOOLS
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: ALL_TOOLS.map((def) => def.tool),
    }));
  • Helper - NinjaOneClient.get() method that performs the actual HTTP GET request to the API
    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, so the description carries full burden. It only states 'list all available device/node roles' without disclosing any behavioral traits like read-only, authentication needs, or rate limits.

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, no redundant information. Every word is necessary.

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 output schema and zero parameters, the description is largely complete for a simple list operation. However, it could briefly mention that no arguments are needed.

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 tool has no parameters, and schema coverage is 100%. The description does not need to add parameter info; it correctly indicates the scope ('all available') which adds meaning.

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 uses a specific verb ('List') and resource ('device/node roles'), clearly distinguishing it from sibling list tools that list different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The purpose is implied but lacks any context or exclusions.

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