Skip to main content
Glama
zebbern

Zebbern Kali MCP

by zebbern
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

callback_clear

Clear all stored HTTP and DNS callback entries from the catcher's memory while keeping listeners active. Get a confirmation with the number of cleared entries.

Instructions

Clear all captured callbacks from the catcher's memory.

Removes all stored HTTP and DNS callback entries. The listeners continue running — only the stored data is cleared.

Returns: Confirmation with the count of cleared entries.

Example: callback_clear()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Discloses that only stored data is cleared, listeners continue running, and returns confirmation with count. No annotations to conflict, but could mention permanence.

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

Conciseness5/5

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

Two short sentences plus example, no wasted words. Front-loaded purpose.

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

Completeness5/5

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

Complete for a simple clear operation with output schema implied: explains what it clears, what stays, and the return value.

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

Parameters5/5

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

No parameters exist; schema coverage is 100%. Description adds no parameter info, but none needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Clear all captured callbacks from the catcher's memory' with specific verb and resource. It distinguishes from siblings like callback_stop by noting listeners continue running.

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?

Description implies usage for clearing stored callbacks without stopping listeners, but lacks explicit when-not or alternatives beyond the sibling context.

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