Skip to main content
Glama

ninja_reset_alert

Dismiss an alert using its unique ID and optionally attach a resolution note to the activity log.

Instructions

Reset (dismiss) an alert by its UID. Optionally provide activityData to record a resolution note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesAlert UID
activityDataNoResolution note to attach to the activity log entry

Implementation Reference

  • The handler function for ninja_reset_alert that resets/dismisses an alert by UID. If activityData is provided, it sends a POST to /alert/{uid}/reset with the resolution note; otherwise it sends a DELETE to /alert/{uid}.
    {
      tool: {
        name: 'ninja_reset_alert',
        description:
          'Reset (dismiss) an alert by its UID. Optionally provide activityData to record a resolution note.',
        inputSchema: {
          type: 'object',
          required: ['uid'],
          properties: {
            uid: { type: 'string', description: 'Alert UID' },
            activityData: {
              type: 'string',
              description: 'Resolution note to attach to the activity log entry',
            },
          },
        },
      },
      handler: async ({ uid, activityData }, client: NinjaOneClient) =>
        activityData
          ? client.post(`/alert/${uid}/reset`, { activityData })
          : client.delete(`/alert/${uid}`),
    },
  • Input schema for ninja_reset_alert tool requiring 'uid' (string) and optionally 'activityData' (string) for resolution note.
    {
      tool: {
        name: 'ninja_reset_alert',
        description:
          'Reset (dismiss) an alert by its UID. Optionally provide activityData to record a resolution note.',
        inputSchema: {
          type: 'object',
          required: ['uid'],
          properties: {
            uid: { type: 'string', description: 'Alert UID' },
            activityData: {
              type: 'string',
              description: 'Resolution note to attach to the activity log entry',
            },
          },
        },
      },
  • The ninja_reset_alert tool is defined as part of the alertTools array which is exported and then registered via ALL_TOOLS in src/tools/index.ts, which is consumed by src/index.ts to build the tool map.
    export const alertTools: ToolDef[] = [
      {
        tool: {
          name: 'ninja_list_alerts',
          description:
            'Get all active alerts across all devices. Filter by source type or device filter expression.',
          inputSchema: {
            type: 'object',
            properties: {
              sourceType: { type: 'string', description: 'Alert source type filter' },
              df: { type: 'string', description: 'Device filter expression' },
              lang: { type: 'string', description: 'Language tag for localized messages (e.g. en)' },
              tz: { type: 'string', description: 'Time zone for timestamps (e.g. America/Chicago)' },
            },
          },
        },
        handler: async (args, client: NinjaOneClient) => client.get('/alerts', clean(args)),
      },
      {
        tool: {
          name: 'ninja_reset_alert',
          description:
            'Reset (dismiss) an alert by its UID. Optionally provide activityData to record a resolution note.',
          inputSchema: {
            type: 'object',
            required: ['uid'],
            properties: {
              uid: { type: 'string', description: 'Alert UID' },
              activityData: {
                type: 'string',
                description: 'Resolution note to attach to the activity log entry',
              },
            },
          },
        },
        handler: async ({ uid, activityData }, client: NinjaOneClient) =>
          activityData
            ? client.post(`/alert/${uid}/reset`, { activityData })
            : client.delete(`/alert/${uid}`),
      },
    ];
Behavior3/5

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

No annotations provided, so the description must carry the full burden. It communicates that the action is a state change (dismiss), but does not disclose any side effects, permissions needed, or consequences (e.g., whether the alert is deleted or archived).

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?

Two short sentences, front-loaded with the primary action, no redundant information.

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, the description does not explain the return value or confirmation. However, for a simple mutation, the action is clear and the optional parameter is explained. Could be improved by mentioning that the UID must correspond to an existing alert.

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 coverage is 100%, so the description adds minimal value beyond the schema. It restates that activityData is for a resolution note, which matches the schema description. No additional meaning provided for uid.

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?

Clearly states the verb 'Reset (dismiss)' and the resource 'alert by its UID'. Differentiates from sibling tools like ninja_list_alerts, which only list alerts, and other mutation tools.

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?

Indicates optional parameter activityData for resolution notes, implying when to use it. However, lacks explicit context on prerequisites (e.g., obtaining UID from list) or when not to use this tool versus alternatives.

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