Skip to main content
Glama

Create Front_port

netbox_create_front_port

Create a new front port on a NetBox device by specifying device, name, type, and rear port mapping.

Instructions

Create a new front_port 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
nameYesFront port name (required).
tagsNoOptional array of tag slugs to apply to the object.
typeYesPort type slug, e.g. '8p8c', 'lc', 'lc-pc', 'sc', 'st', 'mpo', 'fc', 'splice'. (required).
colorNo
labelNo
device_idYesDevice id (required). Exposed as device_id (not device) for the remote-devices bridge; mapped to the API field device on write.
rear_portYesRear port id this front port maps to (required).
descriptionNo
custom_fieldsNoOptional object of custom-field slugs -> values. Only include fields defined on your NetBox instance.
mark_connectedNo
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
rear_port_positionNoPosition on the rear port (default 1).
Behavior4/5

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

Annotations indicate this is a write operation (readOnlyHint=false). The description confirms it adds a new row and suggests a dry-run, adding context beyond annotations. No contradictions detected.

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 concise with three sentences, each serving a distinct purpose. It could be slightly improved by front-loading the return format, but overall it is efficient and free of fluff.

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?

The description covers return format (markdown or JSON) but lacks details on error handling, prerequisites, or constraints like ensuring the device and rear_port exist. For a tool with 12 parameters and no output schema, this is adequate but not thorough.

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?

The description does not elaborate on any parameters. Although the input schema has 67% description coverage, the description adds no additional semantic value for parameters, missing an opportunity to explain complex fields like color or custom_fields.

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 the verb 'Create' and resource 'front_port' in NetBox. It distinguishes from siblings like netbox_update_front_port and netbox_list_front_ports by being the only creation tool for this resource.

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 advises to 'Ask before calling if the user wanted a dry-run', which gives usage context. However, it does not explicitly state when to use this tool vs alternatives or prerequisites like needing a valid device_id.

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