mcp-pihole

get_top_domains

Retrieve top queried domains from Pi-hole, either permitted or blocked, with configurable count up to 100.

Instructions

Get top queried domains.

count: number of domains to return (max 100). blocked: if True, returns top blocked domains instead of top permitted.

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

Input Schema

Name	Required	Description	Default
`count`	No
`blocked`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that count has a max of 100 and explains the effect of the blocked parameter (returns top blocked instead of permitted). This adds value beyond the schema.

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?

The description is extremely concise: one line for purpose and two lines for parameter explanations. No wasted words; every sentence adds 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?

The tool is simple (2 params, no output schema). The description covers the purpose and parameter behavior. It does not mention the return format, but for a 'get' tool returning a list of domains, this is a minor gap. Overall, it is nearly complete.

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?

Schema coverage is 0%, so the description must compensate. It fully explains both parameters: count (with max 100) and blocked (effect). This provides essential meaning not present in 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 'Get top queried domains.' This is a specific verb-resource pair. Among siblings, it distinguishes itself from 'get_domains' (likely all domains) and 'get_top_clients' (different resource).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'search_domains' or 'get_domains'. The description does not provide contexts for selecting between blocked=true/false or comparing to other tools.

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