Skip to main content
Glama

list_alert_conditions

Retrieve all configured alert triggers in NinjaOne to monitor system events and manage notifications effectively.

Instructions

List all configured alert conditions (triggers) in NinjaOne.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNoNumber of conditions to return

Implementation Reference

  • Handler function for 'list_alert_conditions' tool - makes API call to /conditions endpoint and returns JSON results
    async ({ page_size }) => {
      const params: Record<string, string> = {
        pageSize: String(page_size),
      };
    
      try {
        const results = await client.get("/conditions", params);
        return toolResult(JSON.stringify(results, null, 2));
      } catch (error) {
        return toolResult(
          `Error listing alert conditions: ${error}`,
          true,
        );
      }
    },
  • Input schema for 'list_alert_conditions' tool using Zod - defines optional page_size parameter with default value of 100
    {
      page_size: z
        .number()
        .optional()
        .default(100)
        .describe("Number of conditions to return"),
    },
  • Complete registration of 'list_alert_conditions' tool with MCP server - includes name, description, schema, and handler
    server.tool(
      "list_alert_conditions",
      "List all configured alert conditions (triggers) in NinjaOne.",
      {
        page_size: z
          .number()
          .optional()
          .default(100)
          .describe("Number of conditions to return"),
      },
      async ({ page_size }) => {
        const params: Record<string, string> = {
          pageSize: String(page_size),
        };
    
        try {
          const results = await client.get("/conditions", params);
          return toolResult(JSON.stringify(results, null, 2));
        } catch (error) {
          return toolResult(
            `Error listing alert conditions: ${error}`,
            true,
          );
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details such as pagination behavior, rate limits, authentication needs, or what 'configured alert conditions' entails. This leaves gaps in understanding how the tool operates beyond its basic purpose.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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?

Given the tool's low complexity (one optional parameter, no output schema), the description is minimally adequate. However, without annotations or output schema, it lacks details on behavioral traits and return values, which could be important for a list operation in a system with sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the single parameter 'page_size' well-documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for adequate but not enhanced coverage.

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 ('all configured alert conditions (triggers) in NinjaOne'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_alerts' or 'list_device_alerts', which appear related but target different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'list_alerts' and 'list_device_alerts' present, there's no indication of how this tool differs in scope or context, leaving usage ambiguous.

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/fredriksknese/mcp-ninjaone'

If you have feedback or need assistance with the MCP directory API, please join our Discord server