Skip to main content
Glama
Sign In
packmate-mcp

packmate-mcp

by umbra2728
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_pattern

Remove a specific pattern from the network traffic analyzer to maintain an accurate rule set.

Instructions

Delete a pattern.

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>"
    },
    "name": "delete_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
pattern_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only repeats the operation without disclosing effects like irreversibility, cascading deletions, or permission requirements. This is insufficient for a mutation tool.

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

Conciseness2/5

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

The description is extremely concise (two words) but it is under-specified. While brief, it lacks crucial context that would help an agent, making it too minimal to be truly helpful.

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

Completeness1/5

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

Given the tool is a deletion operation with one parameter and an output schema, the description should explain return values, side effects, and how it differs from sibling tools like 'update_pattern' or 'create_pattern'. The single sentence fails to provide any of this context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to the 'pattern_id' parameter. It does not explain what a pattern ID is or how to obtain it, so the description fails to compensate for the missing schema documentation.

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 states the verb 'Delete' and the resource 'a pattern', clearly indicating the tool's action. However, it does not differentiate from sibling tools like 'delete_service' or 'update_pattern', but the operation is distinct enough given the resource name.

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 is provided on when to use this tool versus alternatives, or what prerequisites are needed. There is no mention of checking if a pattern exists or what happens on deletion.

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