Skip to main content
Glama
Sign In
pihole-mcp

pihole-mcp

by chris2ao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_config_item

Remove a value from a Pi-hole array setting with optional preview. Set confirm=true to apply and restart Pi-hole.

Instructions

Remove one value from an array setting. Preview unless confirm=true.

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": {
      "element": "<element>",
      "value": "<value>"
    },
    "name": "remove_config_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
confirmNo
elementYes
restartNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the important safety mechanism that the default is a preview and mutation requires confirm=true, which is genuine behavioral value. But it is silent on the restart parameter's side effect, whether the removal is reversible, and any auth or service-impact requirements.

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 tight sentences, zero waste, with the core action front-loaded ahead of the preview/confirm caveat. Nothing extraneous.

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?

An output schema exists, so return values need not be explained. But for a 4-parameter mutation tool with 0% schema coverage and no annotations, leaving the restart parameter entirely undocumented is a meaningful gap in what an agent needs to invoke it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains confirm (implicitly via 'Preview unless confirm=true') and gestures at element/value ('one value from an array setting'), but says nothing about the restart parameter, which defaults to true and likely has a significant service effect.

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?

States a specific verb and scope: 'Remove one value from an array setting.' This distinguishes it from add_config_item and update_config, which operate on config more broadly. It's clear, though it doesn't explicitly name a sibling or clarify the relationship to update_config.

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?

'Preview unless confirm=true' gives concrete operational guidance on how the tool behaves by default versus when it actually mutates. It does not, however, say when to prefer this over update_config or add_config_item for editing arrays.

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

Deploy Server

Other Tools