Skip to main content
Glama

List Power_feeds

netbox_list_power_feeds
Read-onlyIdempotent

List power feeds from NetBox with pagination and filters by name, site, rack, panel, status, type, and more.

Instructions

List power feeds (a circuit from a panel to a rack) from NetBox.

Supports pagination and filtering. Common patterns:

  • Discovery: call with no filters to browse the first power_feeds.

  • Lookup by id: use netbox_get_power_feed instead when you already have an id.

  • Narrow scan: combine 'q' (fuzzy text) with resource-specific filters below.

Pagination:

  • 'limit' (max 1000, default 50) and 'offset'. Response includes 'has_more' and 'next_offset'.

  • Large list responses auto-truncate to keep under the character limit; keep calling with next_offset to continue.

Resource-specific filters:

  • name: Exact feed name.

  • power_panel_id: Filter by power panel id.

  • rack_id: Filter by rack id.

  • site_id: Filter by site id.

  • status:

  • type:

  • supply:

  • phase:

  • tenant_id: Filter by tenant id.

Universal filters:

  • q (string) Fuzzy text search across searchable fields.

  • tag (string[]) AND-filter by tag slugs.

  • created_after (date) ISO-8601 lower bound on 'created'.

  • created_before (date) ISO-8601 upper bound on 'created'.

Returns: Markdown summary (default) or JSON with shape: { total, count, offset, limit, items: [...], has_more, next_offset? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFuzzy full-text search across the object's searchable fields (name, description, etc.).
tagNoFilter to objects that have ALL of these tag slugs. Repeat for multiple tags (AND semantics in NetBox).
nameNoExact feed name.
typeNo
limitNoMaximum number of items to return per page (1-1000, default 50).
phaseNo
offsetNoNumber of items to skip for pagination. Use next_offset from a previous response.
statusNo
supplyNo
rack_idNoFilter by rack id.
site_idNoFilter by site id.
tenant_idNoFilter by tenant id.
created_afterNoISO-8601 date; only return objects created on or after this date (e.g. 2024-01-01).
created_beforeNoISO-8601 date; only return objects created on or before this date.
power_panel_idNoFilter by power panel id.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive; description adds pagination behavior (auto-truncate, has_more, next_offset) and response format details, which are beyond annotations.

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?

Well-structured with sections: description, patterns, pagination, filters, returns. Front-loaded with key purpose and patterns. No redundant sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 16 parameters, no output schema, and rich annotations, the description covers all filters, pagination, response format, and common use cases. Exceptionally complete.

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

Parameters4/5

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

Groups filters into resource-specific and universal, explains common patterns, and adds descriptions for parameters that have no schema description (e.g., type, status, supply, phase). Schema coverage 75% so description compensates.

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 the resource (power feeds) and action (list), includes a parenthetical definition, and distinguishes from sibling netbox_get_power_feed for lookup by id.

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

Usage Guidelines5/5

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

Explicitly patterns: Discovery (no filters), Lookup by id (use get instead), Narrow scan (combine q with filters). Also describes pagination usage.

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