Skip to main content
Glama

thanaton_expose_port

Allocate an ephemeral Layer 4 TCP forwarding port from a host pool to expose a microVM's internal PostgreSQL, gRPC, or custom daemon to external clients.

Instructions

Allocate and expose a Layer 4 TCP wire forwarding port (antinat) from ephemeral host pool (12000-20000) for PostgreSQL, gRPC, or custom daemons.

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>",
      "guest_port": "<guest_port>"
    },
    "name": "thanaton_expose_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
protocolNoLayer 4 transport protocoltcp
guest_portYesInternal port inside microVM (e.g. 5432, 8080)
sandbox_idYesTarget sandbox ID
service_nameNoDescriptive service name (e.g. postgres, grpc)custom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context that the schema lacks: the host port is ephemeral and auto-picked from a 12000-20000 pool, and traffic is Layer 4 TCP forwarded to the guest port. It omits whether the exposed port is publicly reachable, whether the allocation is idempotent, whether ports persist across sandbox restarts, and any quota/limit considerations.

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

Conciseness4/5

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

A single front-loaded sentence that packs purpose, transport layer, port-pool mechanics, and target workloads with no filler sentences. The parentheticals "(antinat)" and "(12000-20000)" are dense but the jargon term adds little for an agent, keeping it just short of ideal.

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

Completeness3/5

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

For a 4-parameter creation tool with no annotations and no output schema, the description covers the mechanism well but not the outcome: it never says the allocated host port is returned, which is the single most important thing an agent needs after calling. Prerequisites and lifecycle (what closes the port, whether it survives restarts) are also unaddressed.

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 description coverage is 100% and every parameter carries its own description and examples (5432, 8080), so the schema already does the heavy lifting and the baseline is 3. The description adds only workload context (PostgreSQL, gRPC, custom daemons) that loosely maps to service_name and guest_port choices, without defining protocol semantics or defaults beyond what the schema states.

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 uses a specific verb pair ("allocate and expose") on a concrete resource ("Layer 4 TCP wire forwarding port") and states the mechanics (host pool 12000-20000 forwarding to an internal guest port). It is clearly distinct from list_ports or close_port by operation type, though it never names a sibling to reinforce the boundary.

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 only implied through example workloads (PostgreSQL, gRPC, custom daemons), which does tell an agent this is for exposing a listening service inside a sandbox. There is no explicit when-to-use or when-not-to-use guidance, no mention of the related close_port/list_ports flow, and no stated prerequisites such as the sandbox needing to be running.

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