Skip to main content
Glama

thanaton_close_port

Close an active Layer 4 TCP port forward and release its allocated host port back to the sandbox pool.

Instructions

Close an active Layer 4 TCP port forwarding and return the host port to the pool.

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": {
      "sandbox_id": "<sandbox_id>",
      "host_port": "<host_port>"
    },
    "name": "thanaton_close_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_portYesAllocated host port number to release
sandbox_idYesTarget sandbox ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses one meaningful side effect (the host port is released back to the pool), but says nothing about whether traffic is immediately dropped, whether the call is idempotent or errors on an unknown port, what permissions are needed, or what the response contains. For a destructive mutation with zero annotation coverage, this is a substantial gap.

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?

A single sentence with zero waste; the action is front-loaded and the side effect follows immediately. Nothing is redundant or padded.

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

Completeness4/5

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

For a simple two-parameter teardown with a fully documented schema and no output schema, the description covers what the tool does and its main side effect. Missing only edge-case behavior (idempotency, failure modes) that would matter for an agent handling errors.

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

Parameters3/5

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

Schema coverage is 100%, with both sandbox_id and host_port documented in the schema itself, so the baseline is 3. The description adds only marginal meaning ('return the host port to the pool') and no format or constraint details beyond the schema.

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?

States a specific verb ('Close') and a precise resource ('active Layer 4 TCP port forwarding'), plus the effect of returning the host port to the pool. An agent can distinguish this from the inverse operation thanaton_expose_port without opening the schema, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it is clearly the teardown counterpart to exposing a port, and the word 'active' suggests it applies only to existing forwardings. There is no explicit when-to-use/when-not guidance, no mention of what to do if the port is not currently forwarded, and no named alternative.

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