Extract JA3/JA3S TLS fingerprints from pcap files and optionally match them against local user-maintained lists to surface leads.
[Forensics] Extract JA3/JA3S TLS fingerprints and optionally match local user-maintained lists. Treat matches as leads.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| pcap_file | Yes |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-derivable context: matching is optional, it runs against user-maintained local lists, and hits should be treated as leads rather than confirmed findings. It stops short of disclosing what the limit bounds or how results are ordered.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the forensics tag and the verb+resource, with no filler. It is efficient but borders on cryptic — the compressed phrasing leaves key operational detail unstated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description should explain the shape of the return (fingerprint records, hash values, matched-list hits), and it does not. Combined with undocumented parameters, an agent knows what the tool is for but not what it will get back or how to size the request.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry parameter meaning and it does not. pcap_file is inferable from its name, but 'limit' (default 100) is never explained in either place — it is unclear whether it caps fingerprints, matched flows, or packets scanned.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Extract) and resource (JA3/JA3S TLS fingerprints), plus the optional list-matching behavior. No sibling tool produces TLS fingerprints, so the agent can distinguish it from wireshark_decrypt_tls, wireshark_verify_ssl_decryption, and the generic extract_* tools without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The [Forensics] tag and the fingerprint subject imply the use case (TLS client/server fingerprint profiling of a capture), but no when-to-use condition, prerequisite, or named alternative is given. 'Treat matches as leads' is interpretive guidance rather than routing guidance, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.