Skip to main content
Glama
Sign In
packmate-mcp

packmate-mcp

by umbra2728
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pattern_lookback

Apply a saved pattern to network streams captured within the last N minutes to retroactively scan recent traffic.

Instructions

Apply a pattern to streams captured in the last N minutes (N >= 1).

Useful after creating a new pattern to retroactively scan recent traffic.

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": {
      "pattern_id": "<pattern_id>",
      "minutes": "<minutes>"
    },
    "name": "pattern_lookback"
  }
}

Input Schema

NameRequiredDescriptionDefault
pattern_idYes
minutesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It says 'apply a pattern' but does not clarify whether this is a read or write operation, what side effects exist, or what the output looks like. Output schema exists but is not described.

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 description is concise with two sentences and front-loaded with the main action. It could be slightly more efficient, but it is well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the context of sibling tools and lack of annotations, the description covers the tool's purpose and a use case but falls short on behavioral details. It is adequate for a basic understanding but not fully comprehensive.

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?

With 0% schema description coverage, the description adds meaning for 'minutes' by explaining the time range. 'pattern_id' is implied as the pattern to apply, but the description does not directly define it. Some value is added beyond the raw schema.

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?

Description clearly states 'Apply a pattern to streams captured in the last N minutes', specifying verb and resource, and adds a usage scenario. However, it does not explicitly differentiate from sibling tools like create_pattern or update_pattern.

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

Usage Guidelines4/5

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

The description provides a clear use case: 'Useful after creating a new pattern to retroactively scan recent traffic.' This tells the agent when to use the tool, though it lacks explicit exclusions or alternatives.

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