From c357d52fbf32ebfd94c1a7336ff33ec146028271 Mon Sep 17 00:00:00 2001 From: YueGuobin Date: Tue, 12 May 2026 14:36:21 +0800 Subject: [PATCH] fix: document action/query params in PacketAnalysisTool description --- .../gns3_copilot/tools_v2/packet_analysis_tool.py | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/gns3server/agent/gns3_copilot/tools_v2/packet_analysis_tool.py b/gns3server/agent/gns3_copilot/tools_v2/packet_analysis_tool.py index 89e1d30db..0a2966ee5 100644 --- a/gns3server/agent/gns3_copilot/tools_v2/packet_analysis_tool.py +++ b/gns3server/agent/gns3_copilot/tools_v2/packet_analysis_tool.py @@ -71,15 +71,20 @@ class PacketAnalysisTool(BaseTool): Use this to analyze captured packets when diagnosing network issues. - **Before calling this tool**, first query `get_packet_analysis_protocol` - to get the correct tshark field names and display filter for the protocol. - Construct `tshark_args` from the skills data, not from memory. + **Before calling this tool**, use `search_fields` action to look up + valid tshark field names from the live tshark field registry, or query + `get_packet_analysis_protocol` for protocol-level skill definitions. + Construct `tshark_args` using accurate field names. - Input (JSON format): + Input (JSON format) — capture analysis mode: - project_id (str, required): UUID of the GNS3 project - link_id (str, required): UUID of the link to analyze - tshark_args (str, required): tshark command arguments (after '-r ') + Input (JSON format) — field search mode (no capture needed): + - action (str): "search_fields" + - query (str): Protocol or keyword to search (e.g., "ospf", "bgp") + Common tshark argument patterns: -Y "" Display filter -T fields Tab-separated field output