Skip to main content
Glama
Sign In
pihole-mcp

pihole-mcp

by chris2ao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_adlist

Subscribe to a Pi-hole block or allow list URL to manage DNS filtering. Run update_gravity afterward to download the list.

Instructions

Subscribe to an adlist URL. Run update_gravity afterwards to download it.

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": "add_adlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupsNo
addressYes
commentNo
enabledNo
list_typeNoblock

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 behavioral burden. It discloses the important post-condition (the list is not downloaded until update_gravity runs), which is genuine added context, but says nothing about duplicate handling, permission requirements, or whether list_type controls blocking vs allowing.

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 short sentences, front-loaded with the core action and followed by the prerequisite next step. No filler.

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?

Output schema exists so return values need no explanation, and the update_gravity follow-up covers the main operational need. However, with zero annotation coverage and zero schema descriptions across five parameters, the definition is incomplete for correctly configuring the subscription.

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 description coverage is 0% and the description explains none of the five parameters. Only 'address' is implied (a URL), while groups, comment, enabled, and especially the block/allow enum on list_type are left undocumented in both schema and description.

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+resource: 'Subscribe to an adlist URL' makes clear this creates a new adlist subscription, distinguishable from update_adlist, remove_adlist, and list_adlists in the sibling set. It does not explicitly name those siblings, but the operation is unambiguous.

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 a concrete workflow instruction: 'Run update_gravity afterwards to download it.' This tells the agent the action alone is insufficient and what to chain next. It doesn't cover when-not-to-use or the alternative update_adlist, but the conditional next-step guidance is substantive.

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