mcp-infoblox

get_fixed_addresses

Search and list DHCP fixed addresses (reservations) in Infoblox by IPv4, MAC, network, or comment.

Instructions

Search and list DHCP fixed addresses (reservations) 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_fixed_addresses"
  }
}

Input Schema

Name	Required	Description
`ipv4addr`	No	IPv4 address to search for
`mac`	No	MAC address to search for (e.g., 00:11:22:33:44:55)
`network`	No	Network in CIDR to filter by
`network_view`	No	Network view
`comment`	No	Comment to search for (regex)
`max_results`	No	Maximum results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'search and list' but does not disclose whether the operation is read-only, requires special permissions, or has rate limits. Minimal behavioral context.

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?

Single sentence, zero waste. Front-loaded with purpose. Efficient.

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, so description should explain return format or default behavior. It does not. With 6 optional parameters, no indication of default results when no filter is provided. Lacks completeness for a search 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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions, which are already clear. No extra value.

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 'DHCP fixed addresses (reservations) in Infoblox'. It distinguishes from sibling tools like create_fixed_address.

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 tool versus alternatives like search_ip_addresses or get_dhcp_leases. No mention of when not to use or prerequisites.

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