Start a Chisel server to create tunnels for network pivoting, with configurable listening port and reverse tunnel support.
Start a Chisel server for tunneling.
Args: port: Listening port (default: 8080) reverse: Allow reverse tunnels (default: True)
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | ||
| reverse | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It mentions parameters but not behavioral traits like server lifecycle (how it runs, how to stop), network implications, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two sentences plus bullet-like parameter list. Front-loads the main action with no extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple tool with an output schema and two parameters, but lacks details on post-start behavior (e.g., background running, how to stop, output format).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so description adds minimal context: 'Listening port' and 'Allow reverse tunnels' clarify parameter roles beyond the schema's type/default, but defaults are already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Start a Chisel server for tunneling' with a specific verb and resource, distinguishing it from sibling tools like pivot_chisel_client or pivot_ligolo_start.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as pivot_chisel_client or pivot_ligolo_start. The description only explains functionality, not context or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.