VERDICT

by tejcodes-rex

Overview Schema Source Related Servers Discussions Admin

Python

Local

network_dns

Analyze packet captures to identify unique DNS queries and their frequency, supporting digital forensic investigations.

Instructions

Distinct DNS queries with counts.

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": {
      "pcap": "<pcap>"
    },
    "name": "network_dns"
  }
}

Input Schema

Name	Required	Description	Default
`pcap`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It does not mention read-only nature, performance implications, or any prerequisites. The single sentence is insufficient for understanding side effects or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exceptionally concise (one sentence) but lacks necessary details, making it under-specified. While front-loaded, it sacrifices completeness for brevity, which is suboptimal for agent guidance.

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 the absence of annotations and a single parameter, the description fails to cover essential usage context. Although an output schema exists, the input parameter and behavioral aspects remain unexplained, resulting in incomplete guidance.

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

Parameters1/5

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

The parameter 'pcap' has 0% schema description coverage, and the description does not explain what it represents (e.g., file path, raw data). The agent cannot infer the expected format or type, which is critical for correct invocation.

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 'Distinct DNS queries with counts' clearly indicates the tool extracts DNS queries and provides counts, differentiating it from sibling network tools like network_http and network_smtp. However, it does not explicitly state that the input is a pcap file, which is implied by the parameter name but not stated in the description.

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 is provided on when to use this tool versus alternatives such as network_search or network_overview. The description lacks context for choosing this tool, leaving the agent without criteria for selection.

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