Skip to main content
Glama

Update Power_feed

netbox_update_power_feed
DestructiveIdempotent

Update an existing power feed in NetBox by specifying its ID and the fields to change. Fields not provided remain unchanged.

Instructions

Update an existing power_feed 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 power_feed to update.
nameNo
rackNo
tagsNoOptional array of tag slugs to apply to the object.
typeNo
phaseNo
statusNo
supplyNo
tenantNo
voltageNo
amperageNo
commentsNo
descriptionNo
power_panelNo
custom_fieldsNoOptional object of custom-field slugs -> values. Only include fields defined on your NetBox instance.
mark_connectedNo
max_utilizationNo
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
Behavior1/5

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

Description states PATCH semantics (only provided fields changed), suggesting non-destructive behavior. However, annotations set destructiveHint=true, contradicting the described safety. No disclosure of what could be destroyed.

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, each essential: purpose, usage instructions, and return format. No fluff, well-structured with key info front-loaded.

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?

Covers basic usage and return options, but lacks explanation of destructive hint contradiction and deeper parameter semantics. Adequate for a simple update tool, but incomplete given annotation mismatch.

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?

Schema has low description coverage (22%) and 18 parameters. Description adds only the partial update context but does not explain individual parameters beyond what schema already provides (e.g., id, response_format). Fails to compensate for low coverage.

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?

Clearly states 'Update an existing power_feed' with PATCH semantics. The verb and resource are explicit, and it distinguishes from sibling create/get/delete tools.

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?

Describes to supply 'id' and only desired fields, clarifying partial update behavior. However, lacks explicit exclusion or alternative guidance, though siblings imply context.

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