Skip to main content
Glama

ninja_get_device_scripting_options

Retrieve available scripts and built-in actions for a device to see what can be executed.

Instructions

Get available scripts and built-in actions that can be run on a device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID
langNoLanguage tag for localized display names

Implementation Reference

  • The handler function that executes the tool logic. It destructures 'id' from args, passes remaining params to the NinjaOne API via GET /device/{id}/scripting/options, with undefined/empty values cleaned out by the 'clean' utility.
      handler: async ({ id, ...params }, client: NinjaOneClient) =>
        client.get(`/device/${id}/scripting/options`, clean(params)),
    },
  • The input schema validation for the tool. Requires 'id' (number) and optionally accepts 'lang' (string for localized display names).
    inputSchema: {
      type: 'object',
      required: ['id'],
      properties: {
        id: { type: 'number', description: 'Device ID' },
        lang: { type: 'string', description: 'Language tag for localized display names' },
      },
    },
  • The tool is registered as a ToolDef object in the deviceTools array at src/tools/devices.ts. This array is exported and merged into ALL_TOOLS in src/tools/index.ts, which is then used to build a handler map and tool list in src/index.ts.
    {
      tool: {
        name: 'ninja_get_device_scripting_options',
        description: 'Get available scripts and built-in actions that can be run on a device.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Device ID' },
            lang: { type: 'string', description: 'Language tag for localized display names' },
          },
        },
      },
      handler: async ({ id, ...params }, client: NinjaOneClient) =>
        client.get(`/device/${id}/scripting/options`, clean(params)),
    },
  • The 'clean' utility used by the handler to strip undefined/null/empty values from the params before passing them as query parameters to the API.
    export function clean(args: Record<string, any>): Record<string, unknown> {
      return Object.fromEntries(
        Object.entries(args).filter(([, v]) => v != null && v !== ''),
      );
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It indicates a read-only operation but does not disclose potential side effects, permissions, or rate limits. The behavior is typical for a 'get' tool and is not misleading.

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 communicates the tool's purpose without any wasted words, perfectly sized for quick comprehension.

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?

The tool is simple with two parameters and no output schema. The description covers the basic purpose and scope, but could be improved by noting that no output format is provided, or hinting at the structure of returned data.

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% with both parameters described adequately in the schema. The tool description adds no additional meaning beyond what the schema provides, so baseline score applies.

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 clearly states the verb 'Get' and the resource 'available scripts and built-in actions' with the scope 'on a device', distinguishing it from sibling tools like ninja_list_automation_scripts and ninja_run_script.

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 explicit guidance on when to use this tool versus alternatives, such as ninja_list_automation_scripts for global script listing or other device-specific get tools. The description only implies per-device context without stating prerequisites or use cases.

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