Skip to main content
Glama
Sign In
chungus-kali-mcp

chungus-kali-mcp

by cryptopepy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

callback_generate

Generate a callback URL for penetration testing. Use a base URL and optional path prefix to create a unique endpoint for receiving callbacks from target systems.

Instructions

Generate callback URL.

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": {
      "base_url": "<base_url>"
    },
    "name": "callback_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_urlYes
path_prefixNo/cb

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavior, but 'Generate callback URL' offers nothing about side effects, output format, persistence, or required permissions. It fails to convey whether this is a safe, read-only operation or something that creates lasting state.

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 very short, but it is under-specified rather than appropriately concise. A single sentence with no supporting details does not earn its place because it omits critical information needed for correct use.

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?

The tool has no output schema, no annotations, and two parameters with zero description coverage. The description does not explain what a callback URL is, what the tool returns, or how it fits with sibling callback tools, making it inadequate for effective use.

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?

Input schema coverage is 0% and the description does not mention base_url or path_prefix. The agent must guess the meaning of these parameters from their names alone, which is insufficient for reliable invocation.

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 'Generate callback URL' clearly states the core action with a specific verb and resource. It is unambiguous but does not differentiate from sibling callback_* tools or provide context about the URL's purpose, so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives like callback_start or callback_check. The description does not mention any conditions, prerequisites, or exclusions, leaving the agent without context for selection.

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