Skip to main content
Glama

List Prefixes

netbox_list_prefixes
Read-onlyIdempotent

List IP prefixes (subnets) from NetBox with pagination and filtering by CIDR, status, site, VRF, and more. Supports fuzzy search and containment queries.

Instructions

List IP prefixes (subnets) from NetBox.

Supports pagination and filtering. Common patterns:

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

  • Lookup by id: use netbox_get_prefix 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:

  • prefix: Exact CIDR match, e.g. '10.0.0.0/24'.

  • within: Return prefixes strictly contained within this CIDR (e.g. '10.0.0.0/8').

  • within_include: Like 'within' but also includes the parent prefix.

  • contains: Return prefixes that contain this CIDR or IP.

  • family: 4 or 6.

  • status:

  • role_id:

  • site_id:

  • vrf_id: Numeric VRF id; 'null' also matches global.

  • tenant_id:

  • mask_length: Exact prefix length.

  • is_pool:

  • mark_utilized:

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).
limitNoMaximum number of items to return per page (1-1000, default 50).
familyNo4 or 6.
offsetNoNumber of items to skip for pagination. Use next_offset from a previous response.
prefixNoExact CIDR match, e.g. '10.0.0.0/24'.
statusNo
vrf_idNoNumeric VRF id; 'null' also matches global.
withinNoReturn prefixes strictly contained within this CIDR (e.g. '10.0.0.0/8').
is_poolNo
role_idNo
site_idNo
containsNoReturn prefixes that contain this CIDR or IP.
tenant_idNo
mask_lengthNoExact prefix length.
created_afterNoISO-8601 date; only return objects created on or after this date (e.g. 2024-01-01).
mark_utilizedNo
created_beforeNoISO-8601 date; only return objects created on or before this date.
within_includeNoLike 'within' but also includes the parent prefix.
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 readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds transparency about pagination auto-truncation, response format control (markdown vs json), filter behavior (AND semantics for tag), and the meaning of 'null' for vrf_id.

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 clear sections, front-loaded with purpose and common patterns. Every sentence adds value, no redundancy. Efficient use of bullet points and whitespace.

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?

For a 20-parameter listing tool with no required params and no output schema, the description covers all essential behavioral aspects: pagination, filtering categories, response shape, and alternative tools. Leaves no major gaps.

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?

Schema coverage is 70%; the description adds semantics beyond the schema for several parameters (e.g., vrf_id 'null' matches global, tag uses AND semantics, created_after/before are ISO-8601). Also describes response_format parameter clearly.

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 'List IP prefixes (subnets) from NetBox' and distinguishes from netbox_get_prefix via the 'Common patterns' section, explicitly noting when to use that alternative.

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?

Provides explicit when-to-use patterns: discovery with no filters, lookup by id redirect to netbox_get_prefix, and narrow scan with filters. Also explains pagination usage with limit, offset, has_more, and next_offset.

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