Skip to main content
Glama

ninja_update_device_custom_fields

Update custom field values for a device by specifying the device ID and custom field key-value pairs.

Instructions

Update custom field values for a device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID
fieldsYesKey-value pairs of custom field names to their new values

Implementation Reference

  • The handler function that executes the tool logic — calls PATCH /device/{id}/custom-fields with the provided fields object to update custom field values for a device.
      handler: async ({ id, fields }, client: NinjaOneClient) =>
        client.patch(`/device/${id}/custom-fields`, fields),
    },
  • The tool definition including name, description, and inputSchema — requires 'id' (number) and 'fields' (object with key-value pairs of custom field names to values).
    {
      tool: {
        name: 'ninja_update_device_custom_fields',
        description: 'Update custom field values for a device.',
        inputSchema: {
          type: 'object',
          required: ['id', 'fields'],
          properties: {
            id: { type: 'number', description: 'Device ID' },
            fields: {
              type: 'object',
              description: 'Key-value pairs of custom field names to their new values',
              additionalProperties: true,
            },
          },
        },
  • The tool is registered as part of deviceTools which is spread into ALL_TOOLS, then indexed by name into toolMap in src/index.ts via the ListToolsRequestSchema and CallToolRequestSchema handlers.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • The NinjaOneClient.patch method used by the handler to send the HTTP PATCH request to the NinjaOne API.
    async patch<T = unknown>(path: string, body?: unknown): Promise<T> {
      try {
        const res = await this.http.patch<T>(path, body, {
          headers: await this.authHeader(),
        });
        return res.data;
      } catch (err) {
        throw new Error(`PATCH ${path} failed: ${apiError(err)}`);
      }
    }
Behavior2/5

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

Without annotations, the description must fully disclose behavioral traits. It only says 'update' implying mutation, but provides no details on whether updates are additive, destructive, reversible, or require specific permissions.

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?

Single, front-loaded sentence with six words. No unnecessary information; every word is functional.

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 no output schema or annotations, the description lacks enough context about return value, side effects, or error conditions. It is minimally viable but could be more informative.

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%, so baseline is 3. The description adds no additional meaning beyond the schema, such as how the 'fields' object interacts (e.g., partial updates only).

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 'Update custom field values for a device' clearly states the verb (update) and resource (custom field values for a device), distinguishing it from the read-only sibling 'ninja_get_device_custom_fields'.

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 is provided on when to use this tool versus alternatives (e.g., getter), nor any prerequisites or exclusions. The agent must infer usage solely from the description.

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