Skip to main content
Glama

Create Prefix

netbox_create_prefix

Create a new IP prefix in NetBox IPAM by specifying the CIDR and optional attributes such as VRF, role, VLAN, status, or tags.

Instructions

Create a new prefix 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
vrfNoVRF id; omit for the global table.
roleNoPrefix role id.
tagsNoOptional array of tag slugs to apply to the object.
vlanNoVLAN id this prefix belongs to.
prefixYesCIDR, e.g. '10.0.0.0/24' (required).
statusNoactive
tenantNo
is_poolNo
commentsNo
scope_idNoNumeric id of the scope object (e.g. the site id).
scope_typeNoScope object type. NetBox 4.2+ replaced the prefix 'site' field with a generic scope; set together with scope_id.
descriptionNo
custom_fieldsNoOptional object of custom-field slugs -> values. Only include fields defined on your NetBox instance.
mark_utilizedNo
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
Behavior3/5

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

Description discloses that it adds a new row (state change) and mentions return format options. The dry-run ask adds behavioral context beyond annotations. However, it does not discuss error scenarios, required permissions, or idempotency implications.

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?

Description is concise (3 lines), front-loaded with purpose, and includes a structured returns section. Minor redundancy ('new prefix' and 'new row') but overall 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?

Given 15 parameters and no output schema, the description lacks explanation of what a prefix is in NetBox IPAM, relationships to other objects (e.g., VRF, VLAN), or common usage patterns. It meets minimum viability but is 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?

Schema coverage is 60% (moderate), but the description adds no additional meaning for any parameter. Baseline is 3, and no extra value is provided.

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?

Description explicitly states 'Create a new prefix in NetBox', which is a clear verb+resource combination. The tool name reinforces this, so purpose is unambiguous.

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 only usage instruction is 'Ask before calling if the user wanted a dry-run.' There is no guidance on when to use this tool versus related tools (e.g., netbox_update_prefix, netbox_list_prefixes) or any prerequisites or context for invocation.

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