Skip to main content
Glama
Sign In
pihole-mcp

pihole-mcp

by chris2ao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

disable_blocking

Temporarily or indefinitely disable DNS blocking to allow unfiltered access. Specify a duration in seconds for automatic re-enablement.

Instructions

Disable DNS blocking. If duration_seconds is given, re-enables after that timer; otherwise indefinite.

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

Input Schema

NameRequiredDescriptionDefault
duration_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It clearly discloses the two behaviors: indefinite disable if no duration, or temporary disable with auto-re-enable. No contradictions.

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?

Single sentence, front-loaded with the core action. No unnecessary words. Every part is meaningful.

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

Completeness5/5

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

For a simple tool with one optional parameter and an output schema, the description covers all needed context: the two operational modes and the effect of the parameter.

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

Parameters5/5

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

There is only one parameter (duration_seconds) with no schema description (coverage 0%). The description explains its effect: if provided, re-enables after timer; otherwise indefinite. This adds full meaning beyond the schema.

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 ('Disable DNS blocking') and the resource, using a specific verb. It distinguishes from the sibling 'enable_blocking' and adds optional duration behavior.

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?

The description implicitly tells when to use (to disable blocking) and explains the two modes (temporary vs indefinite). However, it does not explicitly exclude alternatives or mention when not to use.

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