zeek-mcp

Overview Schema Source Related Servers Discussions Admin

zeek_query_ssh

Search Zeek SSH connection logs using filters for source/destination IP, authentication status, and connection direction.

Instructions

Search Zeek SSH connection logs. Filter by source/destination IP, authentication status, and connection direction.

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

Input Schema

Name	Required	Description
`dstIp`	No	Destination IP address
`limit`	No	Max results
`srcIp`	No	Source IP address
`timeTo`	No	End time (ISO 8601)
`timeFrom`	No	Start time (ISO 8601)
`direction`	No	Connection direction
`authSuccess`	No	Filter by authentication success/failure

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Jul 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations exist, and the description fails to disclose behavioral traits such as read-only nature, rate limits, or authentication requirements. It only states search/filter, which is insufficient.

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 that is front-loaded with the tool's purpose and efficiently lists key filters without redundancy.

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?

The description omits important parameters like timeFrom, timeTo, and limit, and does not mention what the output contains. With no output schema, more detail is needed.

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?

Schema coverage is 100%, so baseline is 3. The description summarizes some filters (IPs, auth, direction) but adds no significant meaning beyond the schema descriptions.

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 tool searches Zeek SSH connection logs and lists specific filter criteria, distinguishing it from sibling tools that query other protocols.

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 (e.g., zeek_ssh_bruteforce) or when not to use it. The description does not provide any usage context.

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