Skip to main content
Glama
Sign In
mitmproxy-mcp

mitmproxy-mcp

by u33pk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flow_delete

Remove a captured HTTP flow from memory by specifying its flow ID.

Instructions

Delete a flow from memory.

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": {
      "flow_id": "<flow_id>"
    },
    "name": "flow_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

With no annotations, the description must fully disclose behavioral traits. It only states 'Delete a flow from memory,' omitting whether operation is destructive, irreversible, requires permissions, or affects other data. This is insufficient for safe invocation.

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

Conciseness3/5

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

The description is a single sentence with no waste, but it lacks necessary details. It is front-loaded but incomplete, earning a mid-range score.

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

Completeness2/5

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

Given the tool performs a deletion operation and has an output schema, the description should explain return values or side effects. It does not, leaving the agent underinformed compared to similar tools.

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

Parameters2/5

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

The description does not add meaning beyond the schema for the single parameter 'flow_id'. Schema coverage is 0%, yet the description offers no additional context like how to obtain the ID or format constraints.

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 clearly states the verb 'Delete' and the resource 'a flow', and specifies a scope 'from memory'. This distinguishes it from siblings like flow_create or flows_clear, but could be more explicit about the scope's implications.

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 like flows_clear or flow_update. There is no mention of prerequisites, consequences, or conditions that make this tool appropriate.

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