Skip to main content
Glama

Create Device

netbox_create_device

Add a new device to NetBox by providing device type, role, and site. Optionally set tags, serial, status, and other attributes.

Instructions

Create a new device in NetBox.

This adds a new row to NetBox. Ask before calling if the user wanted a dry-run.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faceNoRack face.
nameNoDevice name (may be null for some device types).
rackNo
roleYesDevice role id (required).
siteYesSite id (required).
tagsNoOptional array of tag slugs to apply to the object.
oob_ipNoIP address id for the out-of-band (OOB) management IP.
serialNo
statusNoactive
tenantNo
airflowNoAirflow direction: front-to-rear, rear-to-front, left-to-right, right-to-left, passive, mixed.
clusterNoCluster id if this is a host.
commentsNo
latitudeNoGPS latitude (decimal degrees).
locationNo
platformNo
positionNoRack position in U.
asset_tagNo
longitudeNoGPS longitude (decimal degrees).
descriptionNo
device_typeYesDevice type id (required).
primary_ip4NoIP address id for primary IPv4.
primary_ip6NoIP address id for primary IPv6.
vc_positionNoPosition within the virtual chassis.
vc_priorityNoVirtual chassis master election priority.
custom_fieldsNoOptional object of custom-field slugs -> values. Only include fields defined on your NetBox instance.
config_templateNoConfig template id.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
virtual_chassisNoVirtual chassis id.
local_context_dataNoLocal config context data (JSON object).
Behavior3/5

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

Annotations already indicate non-read-only, non-idempotent, non-destructive. Description adds that it adds a row and mentions return format, but does not disclose additional behavioral traits like auth requirements or side effects beyond creation.

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?

Three sentences with clear front-loading: purpose, caution, return format. No superfluous words.

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?

Despite 30 parameters and complex creation, the description lacks prerequisites (e.g., referenced objects must exist), duplicate handling, and validation rules. The openWorldHint annotation is not leveraged. Incomplete for a complex 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 70% schema description coverage, the schema already documents most parameters. The description only adds return format, not parameter semantics. Baseline of 3 is appropriate.

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 'Create a new device in NetBox' with the verb 'Create' and resource 'device'. It distinguishes from sibling tools like netbox_update_device and netbox_list_devices.

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

Usage Guidelines3/5

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

The description includes 'Ask before calling if the user wanted a dry-run' which provides a precaution but lacks explicit when-to-use or when-not-to-use compared to alternatives. No differentiation from other create tools.

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