Skip to main content
Glama
fredriksknese

mcp-infoblox

create_dhcp_range

Define DHCP IP address ranges in Infoblox NIOS to automate network configuration and IP address assignment for devices.

Instructions

Create a DHCP range (scope) in Infoblox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_addrYesStart IP address of the range
end_addrYesEnd IP address of the range
networkNoNetwork the range belongs to (CIDR)
network_viewNoNetwork view
commentNoComment
memberNoDHCP member to serve this range

Implementation Reference

  • The handler function for create_dhcp_range tool. It builds a data object with start_addr, end_addr, and optional fields (network, network_view, comment, member), then calls client.create('range', data) to create the DHCP range in Infoblox. Returns success message with reference or error message.
    async ({
      start_addr,
      end_addr,
      network,
      network_view,
      comment,
      member,
    }) => {
      const data: Record<string, unknown> = {
        start_addr,
        end_addr,
      };
      if (network) data.network = network;
      if (network_view) data.network_view = network_view;
      if (comment) data.comment = comment;
      if (member) data.member = member;
    
      try {
        const ref = await client.create("range", data);
        return toolResult(
          `DHCP range created successfully.\nReference: ${ref}`,
        );
      } catch (error) {
        return toolResult(
          `Error creating DHCP range: ${error}`,
          true,
        );
      }
    },
  • Zod schema definition for create_dhcp_range tool input. Defines required fields (start_addr, end_addr) and optional fields (network, network_view, comment, member) with descriptions for each parameter. The member field is a nested object with _struct and name properties.
      start_addr: z
        .string()
        .describe("Start IP address of the range"),
      end_addr: z
        .string()
        .describe("End IP address of the range"),
      network: z
        .string()
        .optional()
        .describe("Network the range belongs to (CIDR)"),
      network_view: z
        .string()
        .optional()
        .describe("Network view"),
      comment: z.string().optional().describe("Comment"),
      member: z
        .object({
          _struct: z
            .literal("dhcpmember")
            .default("dhcpmember"),
          name: z.string().describe("Grid member FQDN"),
        })
        .optional()
        .describe("DHCP member to serve this range"),
    },
  • Complete tool registration for create_dhcp_range using server.tool(). Includes the tool name 'create_dhcp_range', description 'Create a DHCP range (scope) in Infoblox', the Zod schema for input validation, and the async handler function.
    server.tool(
      "create_dhcp_range",
      "Create a DHCP range (scope) in Infoblox",
      {
        start_addr: z
          .string()
          .describe("Start IP address of the range"),
        end_addr: z
          .string()
          .describe("End IP address of the range"),
        network: z
          .string()
          .optional()
          .describe("Network the range belongs to (CIDR)"),
        network_view: z
          .string()
          .optional()
          .describe("Network view"),
        comment: z.string().optional().describe("Comment"),
        member: z
          .object({
            _struct: z
              .literal("dhcpmember")
              .default("dhcpmember"),
            name: z.string().describe("Grid member FQDN"),
          })
          .optional()
          .describe("DHCP member to serve this range"),
      },
      async ({
        start_addr,
        end_addr,
        network,
        network_view,
        comment,
        member,
      }) => {
        const data: Record<string, unknown> = {
          start_addr,
          end_addr,
        };
        if (network) data.network = network;
        if (network_view) data.network_view = network_view;
        if (comment) data.comment = comment;
        if (member) data.member = member;
    
        try {
          const ref = await client.create("range", data);
          return toolResult(
            `DHCP range created successfully.\nReference: ${ref}`,
          );
        } catch (error) {
          return toolResult(
            `Error creating DHCP range: ${error}`,
            true,
          );
        }
      },
    );
  • The toolResult helper function that formats the response content for MCP tools. Takes a text string and optional isError flag, returning an object with content array containing type 'text' and the text content.
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
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 for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't address permission requirements, whether the operation is idempotent, what happens on conflicts, or what the response contains. For a creation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a creation tool and front-loads the essential information. Every word earns its place, with zero redundancy or filler content.

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?

For a creation tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what happens after creation, error conditions, or how this tool relates to other network configuration tools in the system. The agent would need to guess about behavioral aspects and integration context.

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?

The description provides no parameter information beyond what's already in the schema. However, with 100% schema description coverage, all 6 parameters are well-documented in the schema itself. The description doesn't add any context about parameter relationships, constraints, or usage patterns, but the schema provides adequate documentation, justifying the baseline score.

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?

The description clearly states the action ('Create') and resource ('DHCP range (scope) in Infoblox'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'create_network' or 'create_fixed_address', which also create network-related resources in the same system.

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 versus alternatives. With sibling tools like 'create_network' and 'create_fixed_address' available, there's no indication of when a DHCP range is appropriate versus other network configuration options. No prerequisites, exclusions, or complementary tools are mentioned.

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/fredriksknese/mcp-infoblox'

If you have feedback or need assistance with the MCP directory API, please join our Discord server