MCP Pi-hole Server

pihole_get_top_permitted

Retrieve the most frequently allowed domains in Pi-hole to monitor permitted DNS traffic patterns and analyze network activity.

Instructions

Get the top permitted (allowed) domains

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

Input Schema

Name	Required	Description	Default
`count`	No	Number of domains to return (default: 10)
`visualize`	No	Return ASCII art bar chart instead of JSON

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether this requires authentication, what format the data returns in (beyond the 'visualize' parameter hint), whether there are rate limits, or how the data is sourced. This leaves significant behavioral gaps for the agent.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple query tool and gets straight to the point.

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

Completeness2/5

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

Given that this is a query tool with no annotations and no output schema, the description should do more to explain what 'top permitted domains' means (e.g., by time period, query volume, etc.) and what format the data returns in. The current description is too minimal for the agent to fully understand the tool's behavior and output.

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?

The schema description coverage is 100%, with both parameters ('count' and 'visualize') clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline expectation without adding extra value.

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?

The description clearly states the verb 'Get' and the resource 'top permitted (allowed) domains', making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'pihole_get_top_blocked' beyond the 'permitted' vs 'blocked' distinction in the name, which is why it doesn't reach a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'pihole_get_stats' or 'pihole_get_query_log'. It doesn't mention prerequisites, timing considerations, or what context this tool is most appropriate for.

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

Deploy Server