Skip to main content
Glama

ninja_list_boards

List all available ticketing boards to organize and track support tickets in your NinjaOne platform.

Instructions

List all available ticketing boards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition for 'ninja_list_boards'. The handler calls client.get('/ticketing/trigger/boards') to list all ticketing boards. No input args needed (empty schema).
    {
      tool: {
        name: 'ninja_list_boards',
        description: 'List all available ticketing boards.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) =>
        client.get('/ticketing/trigger/boards'),
    },
  • Input schema for 'ninja_list_boards' — empty object with no required properties, as the tool takes no arguments.
    {
      tool: {
        name: 'ninja_list_boards',
        description: 'List all available ticketing boards.',
        inputSchema: { type: 'object', properties: {} },
      },
  • The tool is defined within the ticketingTools array (line 5) which is exported and merged into ALL_TOOLS in src/tools/index.ts (line 18), then registered with the MCP server in src/index.ts (line 24-32).
    {
      tool: {
        name: 'ninja_list_boards',
        description: 'List all available ticketing boards.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) =>
        client.get('/ticketing/trigger/boards'),
    },
  • Imports NinjaOneClient which provides the get/post methods used by the handler.
    import { NinjaOneClient } from '../client.js';
    import { clean } from '../utils.js';
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It does not disclose any behavioral traits like permissions required, side effects, or whether the list is full or paginated. The description is too terse to inform the agent about implications.

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, clear, and efficient sentence with no unnecessary words. It conveys the essential purpose without any fluff.

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?

While the tool is simple with no parameters and no output schema, the description lacks details about the return value structure (e.g., board IDs, names) and any potential limitations. It is minimally adequate but could be more 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, so the description cannot add param info. Per guidelines, a zero-parameter tool gets a baseline of 4. The description correctly implies no input needed.

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 'List all available ticketing boards' uses a specific verb ('List') and resource ('ticketing boards'), clearly distinguishing it from sibling tools like ninja_get_ticket or ninja_list_tickets_by_board.

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 such as ninja_get_ticket_attributes or ninja_get_ticket_form. There is no mention of prerequisites or typical use cases (e.g., getting board IDs before querying tickets).

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