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

chungus-kali-mcp

by cryptopepy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pivot_add_pivot

Add a pivot route for network penetration testing. Specify the pivot name, target network, and interface to route traffic through.

Instructions

Add pivot route.

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": {
      "name": "<name>",
      "network": "<network>",
      "interface": "<interface>"
    },
    "name": "pivot_add_pivot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
networkYes
interfaceYes

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, the description must disclose behavioral traits such as side effects or requirements, but 'Add pivot route' merely restates the tool name and offers no information about what happens when the route is added, whether it is reversible, or what permissions are needed.

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 short, which is concise, but it is under-specified rather than efficiently compact. A single sentence that repeats the tool name does not contribute substantive value.

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?

For a nontrivial network routing operation with three required parameters and no output schema, this description is grossly incomplete. It lacks essential context about routing behavior, parameter format, and prerequisites.

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 does not explain the meaning of 'name', 'network', or 'interface'. The agent has no way to infer what values to provide for these required parameters.

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 action ('Add') and the resource ('pivot route'), and it is distinct from sibling pivot tools that handle tunnels, servers, or listing. However, 'pivot route' is ambiguous and lacks scope or context.

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 about when to use this tool versus the many pivot-related siblings. There are no prerequisites, examples, or alternatives mentioned.

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