mcp-infoblox

get_zones

Search and list DNS authoritative zones in Infoblox by FQDN, DNS view, or zone format to filter results.

Instructions

Search and list DNS authoritative zones in Infoblox

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_zones"
  }
}

Input Schema

Name	Required	Description
`fqdn`	No	Zone FQDN to search for (supports regex)
`view`	No	DNS view to filter by
`zone_format`	No	Zone format: FORWARD, IPv4 (reverse), or IPv6 (reverse)
`max_results`	No	Maximum results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, but the description accurately conveys a read-only search operation. It does not elaborate on pagination, sorting, or rate limits, but the behavior is clear for a simple listing tool.

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?

The description is a single, front-loaded sentence with no unnecessary words. It efficiently communicates the tool's purpose.

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 is adequate but minimal. It does not mention that the operation is read-only, nor does it provide any context about return values or prerequisites. For a simple listing tool, it is sufficient but could be improved.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter already well-described in the schema. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Search and list' and the resource 'DNS authoritative zones', with the platform 'Infoblox'. This effectively distinguishes this tool from sibling tools like create_zone, delete_zone, etc.

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 implies usage for searching and listing zones but provides no explicit guidance on when to use this tool versus alternatives (e.g., global_search, search_dns_records). No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.