Skip to main content
Glama

thanaton_list_ports

Lists active Layer 4 TCP port forwardings for a specified microVM sandbox, helping you inspect exposed ports and verify which forwarded connections are currently available.

Instructions

List all active Layer 4 TCP port forwardings for a specific microVM sandbox.

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

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesTarget sandbox ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key trait that only 'active' forwardings are returned rather than the full configuration history. It does not state that the operation is non-mutating explicitly, nor whether results are paginated or what happens when a sandbox has no ports.

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?

One sentence that front-loads the verb and resource with zero filler. Nothing could be trimmed without losing the 'active' qualifier or the sandbox scoping.

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 one-parameter list tool with no output schema and no annotations, the description conveys enough to call it correctly. Minor gaps remain around error behavior for invalid sandbox IDs and pagination, but these do not block correct invocation.

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?

There is a single required parameter whose schema description ('Target sandbox ID') is fully covered at 100%, so the schema does the heavy lifting. The description reinforces the parameter by stating the listing is 'for a specific microVM sandbox', but adds no format or resolution details beyond that.

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 names a specific verb ('List') and a precise resource ('active Layer 4 TCP port forwardings') scoped to a microVM sandbox. 'Active' plus the list framing distinguishes it from mutation-oriented siblings like thanaton_expose_port and thanaton_close_port, though it never names an alternative 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?

The word 'active' implies using this to inspect currently live port forwardings, and the read-only framing is inferable from 'List'. However, there is no explicit guidance on when to choose this over thanaton_expose_port or thanaton_close_port, and no stated prerequisites for reading a sandbox's ports.

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