Skip to main content
Glama

sniff_packets

Read-only

Captures packet headers briefly on a MikroTik router to inspect live traffic by IP, port, protocol, MAC, or interface without saving data.

Instructions

Captures packet headers for a few seconds with the quick packet sniffer (needs the "sniff" policy).

Notes: Shows headers only (interface, direction, MACs, addresses, protocol, size); nothing is saved on the router. ip_address matches source or destination. port: "53", "80,443" or "1000-2000".

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

Input Schema

NameRequiredDescriptionDefault
portNo
deviceNo
durationNo
interfaceNo
ip_addressNo
ip_protocolNo
mac_addressNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.29.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description focuses on added context: headers only, no data persisted on the router, and bounded capture duration. That 'nothing is saved' note is exactly the kind of behavioral reassurance an agent needs for a capture tool; only return/pagination details are absent, and an output schema exists.

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

Conciseness4/5

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

The core action and its policy requirement are front-loaded in one sentence, with supporting detail in a compact Notes block. There is little waste, though the Notes formatting adds slight visual overhead without extra information beyond the two syntax hints.

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?

For a seven-parameter, zero-required capture tool with an output schema, the description covers the essential safety and scope facts plus filter syntax. It stops short of describing what device and interface select, which would be needed for fully confident invocation of every parameter.

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 0%, so the description must compensate. It does explain two parameters well — ip_address matches source or destination, and port accepts single, comma-separated, or range syntax — but device, interface, ip_protocol, and mac_address get no meaning from either the schema or the description.

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 opens with a specific verb+resource: 'Captures packet headers ... with the quick packet sniffer', and states the key precondition. It is clearly a diagnostic capture operation, distinct from the configuration siblings listed, but it never names or contrasts an alternative tool.

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

Usage Guidelines3/5

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

It states the prerequisite ('needs the "sniff" policy') and the brevity of the capture ('a few seconds'), which implies a quick diagnostic use case. However, there is no explicit when-to-use/when-not-to-use guidance or comparison against other diagnostic approaches.

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