mcp-infoblox

restart_services

Restart DNS or DHCP services on the Infoblox grid to apply configuration changes. Specify a member, service, and restart mode for targeted updates.

Instructions

Restart DNS/DHCP services on the Infoblox grid. Required after configuration changes to take effect.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "restart_services"
  }
}

Input Schema

Name	Required	Description	Default
`member`	No	Specific member FQDN to restart. Omit to restart all members with pending changes.
`service`	No	Which service to restart	ALL
`mode`	No	Restart mode	GROUPED

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations provided. Description only states restart is required, but does not disclose potential downtime, prerequisites, or whether it is destructive. For a restart tool, this is insufficient.

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?

Two concise sentences with key information front-loaded. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks details on impact, expected downtime, and behavior if no member is specified. Adequate for simple usage but incomplete for cautious operation.

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 coverage is 100% with clear parameter descriptions. Description adds no extra meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly specifies verb 'Restart', resource 'DNS/DHCP services on the Infoblox grid', and context 'after configuration changes'. Distinct from sibling tools that are mostly CRUD operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly states when to use ('after configuration changes to take effect'). Implicitly not for other operations, but lacks explicit exclusions or alternatives.

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