Skip to main content
Glama

Update Device

netbox_update_device
DestructiveIdempotent

Update an existing device in NetBox by providing its numeric ID and the fields to modify. Only supplied fields are changed.

Instructions

Update an existing device in NetBox (PATCH semantics — only provided fields are changed).

Supply the numeric 'id' and only the fields you want to change. Omitting a field leaves it unchanged.

Returns: Markdown summary of the updated object (default) or JSON with the full NetBox response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric id of the device to update.
faceNo
nameNo
rackNo
roleNo
siteNo
tagsNoOptional array of tag slugs to apply to the object.
oob_ipNo
serialNo
statusNo
tenantNo
airflowNo
clusterNo
commentsNo
latitudeNo
locationNo
platformNo
positionNo
asset_tagNo
longitudeNo
descriptionNo
device_typeNo
primary_ip4No
primary_ip6No
vc_positionNo
vc_priorityNo
custom_fieldsNoOptional object of custom-field slugs -> values. Only include fields defined on your NetBox instance.
config_templateNo
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
virtual_chassisNo
local_context_dataNo
Behavior4/5

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

The description adds PATCH semantics and response format details beyond annotations. It does not contradict annotations like destructiveHint or idempotentHint, though it could clarify what destructive means here.

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 short and front-loaded with purpose and semantics. The third paragraph on returns is somewhat verbose but still efficient.

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?

While it covers core semantics and usage, the lack of parameter descriptions and output schema leaves gaps. It adequately addresses annotations but could be more complete for a tool with 31 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 13% schema coverage, the description fails to explain most parameters. It mentions response_format explicitly but provides no extra meaning for the other 30 parameters.

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 it updates an existing device in NetBox with PATCH semantics, distinguishing it from create and delete siblings. The verb 'update' and resource 'device' are explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It instructs to supply only the numeric 'id' and fields to change, and notes omitting leaves fields unchanged. It mentions response format options but lacks explicit exclusions or when-not-to-use.

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/ZenixSolutions/netbox-mcp-server'

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