mcp-infoblox

create_dhcp_range

Create a DHCP range in Infoblox by specifying start and end IP addresses to automate IP assignment for clients.

Instructions

Create a DHCP range (scope) in Infoblox

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": {
      "start_addr": "<start_addr>",
      "end_addr": "<end_addr>"
    },
    "name": "create_dhcp_range"
  }
}

Input Schema

Name	Required	Description
`start_addr`	Yes	Start IP address of the range
`end_addr`	Yes	End IP address of the range
`network`	No	Network the range belongs to (CIDR)
`network_view`	No	Network view
`comment`	No	Comment
`member`	No	DHCP member to serve this range

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, and the description only states the creation action without any behavioral details (e.g., whether it is idempotent, requires network view, or what happens if the range overlaps). The agent lacks critical behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it is underspecified. The brevity does not add value; it just states the obvious.

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?

Given the tool's complexity (6 parameters, nested object, no output schema), the description is insufficient. It fails to explain the scope concept, prerequisites, or the implications of creating a range.

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?

With 100% schema description coverage, the baseline is 3. The description does not add any additional meaning beyond what the schema already provides, so it remains at baseline.

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 explicitly states the verb 'Create' and identifies the resource as 'DHCP range (scope) in Infoblox'. This clearly differentiates it from sibling tools like create_network or create_host_record.

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?

The description provides no guidance on when to use this tool, nor does it mention any prerequisites or alternatives. The agent has no context to decide between this and other creation tools.

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