Skip to main content
Glama

get_device_processor_info

Retrieve CPU and processor details for a NinjaOne device by providing its device ID to access hardware specifications.

Instructions

Get CPU/processor information for a specific device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYesNinjaOne device ID

Implementation Reference

  • The handler function for get_device_processor_info tool. It takes a device_id parameter, calls the NinjaOne API endpoint `/device/${device_id}/processors`, and returns the processor information as JSON or an error message.
    async ({ device_id }) => {
      try {
        const result = await client.get(`/device/${device_id}/processors`);
        return toolResult(JSON.stringify(result, null, 2));
      } catch (error) {
        return toolResult(
          `Error fetching processor info: ${error}`,
          true,
        );
      }
    },
  • Zod schema definition for the get_device_processor_info tool input. Defines a required device_id parameter as a number with description 'NinjaOne device ID'.
    {
      device_id: z.number().describe("NinjaOne device ID"),
    },
  • Complete tool registration for get_device_processor_info using server.tool(). Includes the tool name, description ('Get CPU/processor information for a specific device.'), input schema, and handler function.
    server.tool(
      "get_device_processor_info",
      "Get CPU/processor information for a specific device.",
      {
        device_id: z.number().describe("NinjaOne device ID"),
      },
      async ({ device_id }) => {
        try {
          const result = await client.get(`/device/${device_id}/processors`);
          return toolResult(JSON.stringify(result, null, 2));
        } catch (error) {
          return toolResult(
            `Error fetching processor info: ${error}`,
            true,
          );
        }
      },
    );
  • Helper function toolResult() that formats the response content for MCP tools. Returns an object with content array containing text type, and optional isError flag for error handling.
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a 'Get' operation, implying read-only behavior, but does not specify permissions, rate limits, error conditions, or response format. This leaves significant gaps for a tool with no annotation coverage.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for its simple function.

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 annotations and output schema, the description is incomplete. It does not explain what CPU/processor information is returned (e.g., model, speed, cores) or handle potential complexities like error cases. For a tool with no structured support, more detail is needed.

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 schema description coverage is 100%, with the parameter 'device_id' fully documented in the schema. The description adds no additional meaning beyond the schema, such as explaining what a 'device_id' represents or how to obtain it, so it meets the baseline for high schema coverage.

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 action ('Get') and the resource ('CPU/processor information for a specific device'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_device' or 'get_device_software', which reduces it from a perfect score.

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, such as 'get_device' for general device info or other device-specific getters. It lacks context on prerequisites or exclusions, leaving usage decisions to inference.

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/fredriksknese/mcp-ninjaone'

If you have feedback or need assistance with the MCP directory API, please join our Discord server