mcp-infoblox

create_aaaa_record

Add an IPv6 DNS AAAA record to Infoblox by specifying the FQDN and IPv6 address, with optional view, TTL, and comment.

Instructions

Create a DNS AAAA (IPv6) record 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": {
      "name": "<name>",
      "ipv6addr": "<ipv6addr>"
    },
    "name": "create_aaaa_record"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	FQDN for the AAAA record
`ipv6addr`	Yes	IPv6 address for the record
`view`	No	DNS view
`ttl`	No	TTL in seconds
`comment`	No	Comment for the record

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations exist, so the description must disclose behavior. It only states the action, omitting details like whether duplication is allowed, permission requirements, or idempotency.

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 concise sentence that efficiently communicates the purpose with no redundancy.

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?

With 5 parameters, no output schema, and no annotations, the description is too minimal. It doesn't explain return value, error states, or success behavior, leaving the agent underinformed.

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 baseline is 3. The descriptions are standard and don't add meaning beyond field names (e.g., 'FQDN for the AAAA record').

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 clearly states the action (Create) and the resource (DNS AAAA IPv6 record) in a specific system (Infoblox). It differentiates from sibling tools like create_a_record, which handles IPv4.

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 DNS record creation siblings, the agent has no context for selecting this tool.

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