Skip to main content
Glama
fredriksknese

mcp-infoblox

create_a_record

Create DNS A records in Infoblox by specifying hostnames and IPv4 addresses to map domain names to IP addresses for network resolution.

Instructions

Create a DNS A record in Infoblox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFQDN for the A record (e.g., host.example.com)
ipv4addrYesIPv4 address for the record
viewNoDNS view (defaults to 'default')
ttlNoTTL in seconds
commentNoComment for the record
disableNoCreate in disabled state

Implementation Reference

  • Handler function that creates a DNS A record by constructing data object with name, ipv4addr, and optional fields (view, ttl, comment, disable), then calls client.create() and returns success/error result
    async ({ name, ipv4addr, view, ttl, comment, disable }) => {
      const data: Record<string, unknown> = { name, ipv4addr };
      if (view) data.view = view;
      if (ttl !== undefined) {
        data.ttl = ttl;
        data.use_ttl = true;
      }
      if (comment) data.comment = comment;
      if (disable) data.disable = disable;
    
      try {
        const ref = await client.create("record:a", data);
        return toolResult(`A record created successfully.\nReference: ${ref}`);
      } catch (error) {
        return toolResult(`Error creating A record: ${error}`, true);
      }
    },
  • Zod schema defining input validation for create_a_record tool with fields: name (required string), ipv4addr (required string), view (optional string), ttl (optional number), comment (optional string), and disable (optional boolean, defaults to false)
    {
      name: z
        .string()
        .describe("FQDN for the A record (e.g., host.example.com)"),
      ipv4addr: z.string().describe("IPv4 address for the record"),
      view: z
        .string()
        .optional()
        .describe("DNS view (defaults to 'default')"),
      ttl: z.number().optional().describe("TTL in seconds"),
      comment: z.string().optional().describe("Comment for the record"),
      disable: z
        .boolean()
        .optional()
        .default(false)
        .describe("Create in disabled state"),
    },
  • Complete tool registration using server.tool() with name "create_a_record", description, schema, and handler function. This is called within registerDnsTools function.
    server.tool(
      "create_a_record",
      "Create a DNS A record in Infoblox",
      {
        name: z
          .string()
          .describe("FQDN for the A record (e.g., host.example.com)"),
        ipv4addr: z.string().describe("IPv4 address for the record"),
        view: z
          .string()
          .optional()
          .describe("DNS view (defaults to 'default')"),
        ttl: z.number().optional().describe("TTL in seconds"),
        comment: z.string().optional().describe("Comment for the record"),
        disable: z
          .boolean()
          .optional()
          .default(false)
          .describe("Create in disabled state"),
      },
      async ({ name, ipv4addr, view, ttl, comment, disable }) => {
        const data: Record<string, unknown> = { name, ipv4addr };
        if (view) data.view = view;
        if (ttl !== undefined) {
          data.ttl = ttl;
          data.use_ttl = true;
        }
        if (comment) data.comment = comment;
        if (disable) data.disable = disable;
    
        try {
          const ref = await client.create("record:a", data);
          return toolResult(`A record created successfully.\nReference: ${ref}`);
        } catch (error) {
          return toolResult(`Error creating A record: ${error}`, true);
        }
      },
    );
  • Helper utility function that formats tool results in MCP format with content array and error flag
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
  • InfobloxClient.create method that makes POST request to Infoblox API to create objects, used by the handler to create A records
    async create(
      objectType: string,
      data: Record<string, unknown>,
    ): Promise<string> {
      return this.request("POST", objectType, data) as Promise<string>;
    }
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 disclose important behavioral traits like authentication requirements, rate limits, whether the operation is idempotent, what happens on duplicate records, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 communicates the essential purpose without any wasted words. It's appropriately sized for a tool with good schema documentation and gets straight to the point. Every word earns its place in this concise formulation.

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 this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, error conditions, authentication needs, or how it differs from similar sibling tools. For a 6-parameter write operation in a system with many related tools, the description should provide more contextual information to guide proper 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?

Schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples beyond what's in the schema, or clarify edge cases. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't add value beyond the structured data.

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 ('DNS A record in Infoblox'), making the tool's purpose immediately understandable. It distinguishes this as an A record creation tool, which is helpful given the many sibling tools for different record types. However, it doesn't explicitly differentiate from other creation tools beyond the record type.

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 many sibling tools like create_aaaa_record, create_cname_record, and update_dns_record, there's no indication of when this specific A record creation tool is appropriate versus other record types or update operations. The description lacks any context about prerequisites or when-not-to-use scenarios.

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