Skip to main content
Glama

ninja_list_user_roles

Retrieve all user roles defined in NinjaOne to manage permissions and access controls.

Instructions

List all user roles defined in NinjaOne.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'ninja_list_user_roles'. Makes a GET request to /user/roles on the NinjaOne API using the NinjaOneClient.
    {
      tool: {
        name: 'ninja_list_user_roles',
        description: 'List all user roles defined in NinjaOne.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/user/roles'),
    },
  • The input schema for 'ninja_list_user_roles'. No parameters required (empty properties).
    tool: {
      name: 'ninja_list_user_roles',
      description: 'List all user roles defined in NinjaOne.',
      inputSchema: { type: 'object', properties: {} },
    },
  • Tool definition object registered in the userTools array, exported from src/tools/users.ts.
    {
  • ALL_TOOLS aggregates all tool arrays including userTools which contains ninja_list_user_roles.
    import { ticketingTools } from './ticketing.js';
    import { userTools } from './users.js';
    export type { ToolDef } from './types.js';
    
    export const ALL_TOOLS = [
  • The toolMap built from ALL_TOOLS associates the tool name to its handler. At runtime, CallToolRequestSchema dispatches to the correct handler via this map.
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the operation is a read, with no mention of auth requirements, rate limits, or data scope. This is minimally sufficient but not transparent.

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 one concise sentence with no extraneous information. It is efficiently front-loaded.

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?

The description covers the basic purpose but lacks details on output format, pagination, or any required context. For a simple list tool with no parameters and no output schema, it is adequate but not complete.

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, and schema description coverage is 100%. Per guidelines, 0 parameters baseline is 4, and the description correctly indicates no parameters are needed.

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 action (list) and resource (user roles). It distinguishes from sibling list tools by specifying 'user roles' rather than other entities. However, it closely echoes the tool name without adding much context.

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. Given many sibling list tools, the description should indicate when listing user roles is appropriate or preferred, but it does not.

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