mcp-infoblox

get_all_records_in_zone

Retrieve all DNS records in a zone, filtered by type and view, to audit or inventory DNS entries.

Instructions

List all DNS records in a specific zone. Returns all record types in the zone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zone": "<zone>"
    },
    "name": "get_all_records_in_zone"
  }
}

Input Schema

Name	Required	Description
`zone`	Yes	DNS zone name (FQDN)
`view`	No	DNS view
`record_type`	No	Filter by record type: A, AAAA, CNAME, MX, PTR, SRV, TXT, HOST, etc.
`max_results`	No	Maximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations. Description does not disclose behaviors like pagination, latency, permissions, or whether it returns full records vs summaries.

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?

Two concise sentences without fluff. Could be reordered to front-load verb.

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

Completeness2/5

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

No output schema. Description lacks details on return format, pagination, or field contents, making it incomplete for a list tool.

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 covers all parameters with descriptions. Description adds minimal context about default behavior of returning all types, but does not go beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Purpose is clear: list all DNS records in a zone. However, the description says 'Returns all record types' but the schema includes an optional record_type filter, which is slightly inconsistent.

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

Usage Guidelines2/5

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

No guidance on when to use this vs siblings like search_dns_records or get_zones. Does not mention when-not or alternatives.

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