Skip to main content
Glama
fredriksknese

mcp-infoblox

create_aaaa_record

Add an IPv6 address to DNS by creating an AAAA record in Infoblox, specifying the FQDN and IPv6 address.

Instructions

Create a DNS AAAA (IPv6) record in Infoblox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFQDN for the AAAA record
ipv6addrYesIPv6 address for the record
viewNoDNS view
ttlNoTTL in seconds
commentNoComment for the record

Implementation Reference

  • Complete tool registration with handler function that creates AAAA (IPv6) DNS records. The handler constructs the data object with name and ipv6addr as required fields, optionally includes view, ttl (with use_ttl flag), and comment, then calls client.create() to make the API request and returns success/error message.
    server.tool(
      "create_aaaa_record",
      "Create a DNS AAAA (IPv6) record in Infoblox",
      {
        name: z.string().describe("FQDN for the AAAA record"),
        ipv6addr: z.string().describe("IPv6 address for the record"),
        view: z.string().optional().describe("DNS view"),
        ttl: z.number().optional().describe("TTL in seconds"),
        comment: z.string().optional().describe("Comment for the record"),
      },
      async ({ name, ipv6addr, view, ttl, comment }) => {
        const data: Record<string, unknown> = { name, ipv6addr };
        if (view) data.view = view;
        if (ttl !== undefined) {
          data.ttl = ttl;
          data.use_ttl = true;
        }
        if (comment) data.comment = comment;
    
        try {
          const ref = await client.create("record:aaaa", data);
          return toolResult(
            `AAAA record created successfully.\nReference: ${ref}`,
          );
        } catch (error) {
          return toolResult(
            `Error creating AAAA record: ${error}`,
            true,
          );
        }
      },
    );
  • Zod schema defining the input parameters for create_aaaa_record tool: name (required FQDN string), ipv6addr (required IPv6 address string), view (optional DNS view), ttl (optional number in seconds), and comment (optional string).
    {
      name: z.string().describe("FQDN for the AAAA record"),
      ipv6addr: z.string().describe("IPv6 address for the record"),
      view: z.string().optional().describe("DNS view"),
      ttl: z.number().optional().describe("TTL in seconds"),
      comment: z.string().optional().describe("Comment for the record"),
    },
  • src/index.ts:42-42 (registration)
    Registration call in the main entry point that invokes registerDnsTools function, passing the MCP server instance and InfobloxClient instance to register all DNS tools including create_aaaa_record.
    registerDnsTools(server, client);
  • Helper method in InfobloxClient class that makes POST request to create a new object. Called by the handler with objectType 'record:aaaa' and the data object to create the AAAA record via the Infoblox WAPI.
    async create(
      objectType: string,
      data: Record<string, unknown>,
    ): Promise<string> {
      return this.request("POST", objectType, data) as Promise<string>;
    }
  • Helper function that formats the response content for MCP tools. Returns an object with content array containing text and an isError flag, used by the handler to return success or error messages.
    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 the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't address permissions required, whether the operation is idempotent, potential side effects, error conditions, or what happens on success (e.g., returns a record reference). For a mutation tool with zero annotation coverage, this is a significant gap.

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 with zero wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information (action, resource, context). Every word earns its place.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, authentication requirements, or system-specific behaviors. Given the complexity of DNS record creation and the lack of structured metadata, the description should provide more operational 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?

Schema description coverage is 100%, with all 5 parameters well-documented in the schema itself (e.g., 'name' as 'FQDN for the AAAA record', 'ipv6addr' as 'IPv6 address for the record'). The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 when schema coverage is high.

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'), resource type ('DNS AAAA (IPv6) record'), and system context ('in Infoblox'). It distinguishes this tool from siblings like create_a_record (IPv4) and create_cname_record (CNAME), though it doesn't explicitly mention these alternatives. The purpose is specific and unambiguous.

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 like create_a_record or create_host_record, nor does it mention prerequisites, dependencies, or typical use cases. It simply states what the tool does without contextual usage information.

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