Skip to main content
Glama

ninja_get_device_disks

Retrieve physical disk drive information for a specified device using its device ID. Access detailed disk data from the NinjaOne platform.

Instructions

Get physical disk drive information for a device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID

Implementation Reference

  • The handler function for ninja_get_device_disks that calls GET /device/{id}/disks via the NinjaOneClient.
    handler: async ({ id }, client: NinjaOneClient) => client.get(`/device/${id}/disks`),
  • The tool definition including name, description, and inputSchema for ninja_get_device_disks. Requires a numeric 'id' property.
    {
      tool: {
        name: 'ninja_get_device_disks',
        description: 'Get physical disk drive information for a device.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Device ID' },
          },
        },
      },
      handler: async ({ id }, client: NinjaOneClient) => client.get(`/device/${id}/disks`),
    },
  • The tool is exported as part of deviceTools array, which is spread into ALL_TOOLS in src/tools/index.ts for registration with the MCP server.
    export const ALL_TOOLS = [
      ...deviceTools,
  • src/index.ts:31-32 (registration)
    The ALL_TOOLS array is used to build the tool map and register tools with the MCP ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: ALL_TOOLS.map((def) => def.tool),
  • src/index.ts:24-24 (registration)
    The ALL_TOOLS array is used to build a handler map (tool name -> handler) which is looked up in CallToolRequestSchema.
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
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 any behavioral traits beyond the basic operation. It is implied to be a read operation, but lacks explicit transparency about permissions, side effects, or output.

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, concise sentence that is front-loaded with the essential information, containing no unnecessary words.

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 single parameter and no output schema, the description is minimally adequate. It could be more complete by mentioning the type of information returned or any constraints, but it suffices for a simple tool.

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?

With 100% schema description coverage, the baseline is 3. The description does not add any meaning beyond the schema's parameter description of 'Device ID'.

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 'get' and the resource 'physical disk drive information' for a device, making the purpose specific. However, it does not differentiate from sibling tools like 'ninja_query_disks', which may have overlapping functionality.

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, nor does it specify any prerequisites or context for usage.

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