Skip to main content
Glama

ninja_get_device_software

Retrieve a list of installed software on a device to audit or manage applications.

Instructions

Get installed software on a device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID

Implementation Reference

  • Handler function that executes the GET request to /device/{id}/software, returning installed software for a device.
    handler: async ({ id }, client: NinjaOneClient) => client.get(`/device/${id}/software`),
  • Schema definition for ninja_get_device_software tool: requires a numeric device ID, returns installed software list.
    tool: {
      name: 'ninja_get_device_software',
      description: 'Get installed software on a device.',
      inputSchema: {
        type: 'object',
        required: ['id'],
        properties: {
          id: { type: 'number', description: 'Device ID' },
        },
      },
    },
  • Tool registration as part of deviceTools array in src/tools/devices.ts, aggregated into ALL_TOOLS in src/tools/index.ts, and registered with the MCP server via ListToolsRequestSchema/CallToolRequestSchema in src/index.ts.
    {
      tool: {
        name: 'ninja_get_device_software',
        description: 'Get installed software on a device.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Device ID' },
          },
        },
      },
      handler: async ({ id }, client: NinjaOneClient) => client.get(`/device/${id}/software`),
    },
Behavior2/5

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

No annotations are provided, and the description does not disclose read-only behavior, side effects, authentication requirements, or rate limits. It also does not specify the scope of 'installed software' (e.g., system vs user software).

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?

The description is a single sentence with no wasted words. It front-loads the action and resource but is slightly terse.

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?

Given the lack of output schema, the description should indicate what the returned data includes (e.g., software name, version). This is missing. For a simple tool, completeness is lacking.

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?

The input schema has 100% description coverage (one parameter 'id' with description 'Device ID'). The description adds no additional meaning beyond the schema, so baseline 3 applies.

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 verb 'Get' and resource 'installed software on a device' are clear. However, it does not differentiate from the sibling tool 'ninja_query_software' which may return similar data. This ambiguity prevents a score of 5.

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_query_software' or other get_device_* tools. The description lacks any context for selection.

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