Skip to main content
Glama

List Racks

netbox_list_racks
Read-onlyIdempotent

List equipment racks from NetBox with pagination and filtering by name, site, location, status, role, tenant, serial, asset tag, or fuzzy text search.

Instructions

List equipment racks from NetBox.

Supports pagination and filtering. Common patterns:

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

  • Lookup by id: use netbox_get_rack 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 rack name.

  • site_id: Site id.

  • location_id: Location id.

  • status: Rack status.

  • role_id: Rack role id.

  • tenant_id: Tenant id.

  • serial: Exact serial number.

  • asset_tag: Exact asset tag.

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 rack name.
limitNoMaximum number of items to return per page (1-1000, default 50).
offsetNoNumber of items to skip for pagination. Use next_offset from a previous response.
serialNoExact serial number.
statusNoRack status.
role_idNoRack role id.
site_idNoSite id.
asset_tagNoExact asset tag.
tenant_idNoTenant id.
location_idNoLocation 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.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds behavioral details: pagination (limit, offset, has_more, next_offset), auto-truncation for large lists, and response format options (markdown/json). No contradictions.

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?

Well-structured with clear sections (common patterns, pagination, filters, returns). Slightly verbose but each sentence adds value. Could be slightly more concise, but highly organized.

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 15 parameters, zero required, no output schema, the description is complete. Explains all filters, pagination behavior, response shape fields (total, count, has_more, etc.), and even mentions auto-truncation. No gaps.

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

Parameters5/5

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

Schema coverage is 100% but description adds grouping into resource-specific and universal filters, explains pagination parameters, and provides context like 'use next_offset from a previous response'. Adds meaning beyond schema.

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 it lists equipment racks from NetBox, with specific verb and resource. It distinguishes from sibling tools like netbox_get_rack (for ID lookup) and netbox_create_rack, using explicit language like 'use netbox_get_rack instead'.

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 guidance on when to use this tool vs alternatives. Describes three common patterns: discovery (no filters), lookup by id (refer to netbox_get_rack), and narrow scan (combine 'q' with filters). No misleading advice.

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