Skip to main content
Glama
Sign In
pihole-mcp

pihole-mcp

by chris2ao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_adlist

Remove an address from a Pi-hole block or allow list. Preview unless confirm=true; run update_gravity afterward to apply.

Instructions

Unsubscribe from an adlist. Preview unless confirm=true. Run update_gravity afterwards.

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": {
      "address": "<address>"
    },
    "name": "remove_adlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
confirmNo
list_typeNoblock

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well for the critical trait: a destructive operation defaults to a safe preview and requires confirm=true to actually unsubscribe. It also discloses the update_gravity side effect. It omits auth/permission requirements, keeping it at a 4.

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?

Three short imperative sentences, purpose front-loaded, no waste. Each sentence adds actionable value.

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

Completeness4/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. For a destructive tool with no annotations, the description adequately covers the preview/confirm behavior and follow-up step, though address/list_type semantics remain unaddressed.

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 0%, so the description must compensate. It explains the most important parameter (confirm=true triggers actual removal vs preview), but leaves 'address' format and the 'list_type' block/allow enum undocumented in both schema and description.

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?

States a specific verb ('Unsubscribe') and resource ('an adlist'), which cleanly distinguishes it from add_adlist, update_adlist, and list_adlists. An agent can identify the operation without opening the schema.

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?

Gives the key workflow context: it previews by default and only executes with confirm=true, plus a follow-up step ('Run update_gravity afterwards'). It doesn't name alternatives or exclusions, but the two-phase usage is clearly conveyed.

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