Skip to main content
Glama
fredriksknese

mcp-infoblox

create_fixed_address

Reserve a specific IP address for a device by binding it to a MAC address in Infoblox DHCP. This ensures consistent network connectivity and simplifies device management.

Instructions

Create a DHCP fixed address (reservation) in Infoblox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipv4addrYesIPv4 address to reserve
macYesMAC address of the client (e.g., 00:11:22:33:44:55)
nameNoName for the fixed address
commentNoDescription
network_viewNoNetwork view
match_clientNoClient matching methodMAC_ADDRESS
optionsNoDHCP options

Implementation Reference

  • The handler function for 'create_fixed_address' tool. It builds the data object from input parameters and calls client.create('fixedaddress', data) to create a DHCP fixed address reservation in Infoblox. Returns success message with reference or error message.
      async ({
        ipv4addr,
        mac,
        name,
        comment,
        network_view,
        match_client,
        options,
      }) => {
        const data: Record<string, unknown> = { ipv4addr, mac };
        if (name) data.name = name;
        if (comment) data.comment = comment;
        if (network_view) data.network_view = network_view;
        if (match_client) data.match_client = match_client;
        if (options) data.options = options;
    
        try {
          const ref = await client.create("fixedaddress", data);
          return toolResult(
            `Fixed address created successfully.\nReference: ${ref}`,
          );
        } catch (error) {
          return toolResult(
            `Error creating fixed address: ${error}`,
            true,
          );
        }
      },
    );
  • Zod schema definition for 'create_fixed_address' tool inputs. Defines validation for ipv4addr (required), mac (required), name, comment, network_view, match_client (enum with default), and options (array of DHCP option objects).
    {
      ipv4addr: z.string().describe("IPv4 address to reserve"),
      mac: z
        .string()
        .describe(
          "MAC address of the client (e.g., 00:11:22:33:44:55)",
        ),
      name: z
        .string()
        .optional()
        .describe("Name for the fixed address"),
      comment: z
        .string()
        .optional()
        .describe("Description"),
      network_view: z
        .string()
        .optional()
        .describe("Network view"),
      match_client: z
        .enum([
          "MAC_ADDRESS",
          "CLIENT_ID",
          "CIRCUIT_ID",
          "REMOTE_ID",
        ])
        .optional()
        .default("MAC_ADDRESS")
        .describe("Client matching method"),
      options: z
        .array(
          z.object({
            name: z.string().describe("Option name"),
            num: z.number().describe("Option number"),
            use_option: z.boolean().default(true),
            value: z.string().describe("Option value"),
            vendor_class: z.string().default("DHCP"),
          }),
        )
        .optional()
        .describe("DHCP options"),
    },
  • Registration of 'create_fixed_address' tool using server.tool(). Includes tool name, description, input schema, and handler function. Part of the registerDhcpTools function that registers all DHCP-related tools.
    server.tool(
      "create_fixed_address",
      "Create a DHCP fixed address (reservation) in Infoblox",
      {
        ipv4addr: z.string().describe("IPv4 address to reserve"),
        mac: z
          .string()
          .describe(
            "MAC address of the client (e.g., 00:11:22:33:44:55)",
          ),
        name: z
          .string()
          .optional()
          .describe("Name for the fixed address"),
        comment: z
          .string()
          .optional()
          .describe("Description"),
        network_view: z
          .string()
          .optional()
          .describe("Network view"),
        match_client: z
          .enum([
            "MAC_ADDRESS",
            "CLIENT_ID",
            "CIRCUIT_ID",
            "REMOTE_ID",
          ])
          .optional()
          .default("MAC_ADDRESS")
          .describe("Client matching method"),
        options: z
          .array(
            z.object({
              name: z.string().describe("Option name"),
              num: z.number().describe("Option number"),
              use_option: z.boolean().default(true),
              value: z.string().describe("Option value"),
              vendor_class: z.string().default("DHCP"),
            }),
          )
          .optional()
          .describe("DHCP options"),
      },
      async ({
        ipv4addr,
        mac,
        name,
        comment,
        network_view,
        match_client,
        options,
      }) => {
        const data: Record<string, unknown> = { ipv4addr, mac };
        if (name) data.name = name;
        if (comment) data.comment = comment;
        if (network_view) data.network_view = network_view;
        if (match_client) data.match_client = match_client;
        if (options) data.options = options;
    
        try {
          const ref = await client.create("fixedaddress", data);
          return toolResult(
            `Fixed address created successfully.\nReference: ${ref}`,
          );
        } catch (error) {
          return toolResult(
            `Error creating fixed address: ${error}`,
            true,
          );
        }
      },
    );
  • InfobloxClient.create() method used by the handler to make the actual API call. Sends a POST request to create the fixed address object in Infoblox and returns the reference string.
    async create(
      objectType: string,
      data: Record<string, unknown>,
    ): Promise<string> {
      return this.request("POST", objectType, data) as Promise<string>;
    }
  • src/index.ts:44-44 (registration)
    Main entry point calls registerDhcpTools(server, client) to register all DHCP tools including 'create_fixed_address'.
    registerDhcpTools(server, client);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, it doesn't specify whether this requires special permissions, what happens on duplicate entries, whether changes are reversible, or what the typical response looks like. For a tool that creates network configurations with potential production impact, this is a significant gap in safety and operational 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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It front-loads the essential information (create DHCP fixed address) and specifies the system context (Infoblox). Every word earns its place in this compact definition.

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 tool that creates network infrastructure elements with 7 parameters and no output schema, the description is insufficient. It doesn't explain what a 'fixed address' means operationally, how it differs from regular DHCP leases, what validation occurs, or what happens on success/failure. Given the complexity of DHCP configuration and the lack of annotations, more contextual information would be valuable for safe usage.

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 schema description coverage is 100%, providing comprehensive parameter documentation. The description doesn't add any parameter-specific information beyond what's already in the schema. However, it does establish the overall context (DHCP fixed address creation in Infoblox) which helps frame the parameter usage. This meets the baseline for high schema coverage.

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 fixed address (reservation) in Infoblox'), making the purpose immediately understandable. It distinguishes from sibling tools like 'create_dhcp_range' by specifying it's for fixed addresses/reservations rather than ranges. However, it doesn't explicitly contrast with other DHCP-related tools like 'get_fixed_addresses' or 'delete_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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'create_dhcp_range' for dynamic allocations, or when to use it in conjunction with other record creation tools. There's no mention of prerequisites, dependencies, or typical workflows in the Infoblox context.

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