Skip to main content
Glama

ninja_get_device_installed_software_patches

Get the installed software patch history for a device, filtering by install status or date range.

Instructions

Get software patch install history for a device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID
statusNoFilter by install status
installedBeforeNoFilter patches installed before this date
installedAfterNoFilter patches installed after this date

Implementation Reference

  • The handler function that executes the tool logic. Makes a GET request to /device/{id}/software-patch-installs with cleaned params.
    handler: async ({ id, ...params }, client: NinjaOneClient) =>
      client.get(`/device/${id}/software-patch-installs`, clean(params)),
  • Input schema definition for the tool. Requires 'id' (number) and accepts optional filters: status, installedBefore, installedAfter.
    inputSchema: {
      type: 'object',
      required: ['id'],
      properties: {
        id: { type: 'number', description: 'Device ID' },
        status: { type: 'string', description: 'Filter by install status' },
        installedBefore: { type: 'string', description: 'Filter patches installed before this date' },
        installedAfter: { type: 'string', description: 'Filter patches installed after this date' },
      },
    },
  • The tool registration within the deviceTools array. Defines the tool name 'ninja_get_device_installed_software_patches' and its full metadata.
    {
      tool: {
        name: 'ninja_get_device_installed_software_patches',
        description: 'Get software patch install history for a device.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Device ID' },
            status: { type: 'string', description: 'Filter by install status' },
            installedBefore: { type: 'string', description: 'Filter patches installed before this date' },
            installedAfter: { type: 'string', description: 'Filter patches installed after this date' },
          },
        },
      },
      handler: async ({ id, ...params }, client: NinjaOneClient) =>
        client.get(`/device/${id}/software-patch-installs`, clean(params)),
    },
  • The deviceTools array is spread into ALL_TOOLS, which is used by the MCP server to register all tools.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • The ToolDef interface that defines the structure of each tool (tool metadata + handler function).
    export interface ToolDef {
      tool: Tool;
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      handler: (args: any, client: NinjaOneClient) => Promise<unknown>;
    }
Behavior2/5

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

With no annotations provided, the description fails to disclose behavioral traits such as pagination, return format, or side effects. It merely repeats the tool's purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded, but slightly under-specifies behavior. It earns its place, though could include more context without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations; the description is too brief for a tool returning historical data. Missing details like date format, result ordering, or limit information.

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?

Input schema covers all four parameters with descriptions (100% coverage). The description adds no additional meaning beyond what the schema already provides.

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 tool retrieves 'software patch install history for a device,' specifying verb and resource. However, it doesn't differentiate from sister tools like 'ninja_get_device_software_patches' which may also retrieve patch data.

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 (e.g., query vs get tools) or any prerequisites. The agent must infer context from the tool name alone.

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