Skip to main content
Glama

thanaton_pty_info

Retrieve real-time WebSocket PTY gateway connection details for an attached interactive microVM shell using a sandbox ID, enabling direct terminal access inside isolated KVM sandboxes.

Instructions

Get real-time bidirectional WebSocket PTY terminal gateway connection details for an attached interactive microVM shell.

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_pty_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesTarget sandbox ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/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 burden. It usefully discloses that the result is a live bidirectional WebSocket PTY gateway connection, hinting at session-oriented behavior, but omits whether calling it creates or consumes a session, whether credentials/tokens are required, whether connections expire, and whether the call has side effects. Additive context exists but key operational behavior is missing.

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 with no filler, and the key noun phrase (connection details) appears early. It is jargon-dense but every term conveys scope rather than restating the name.

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?

With no output schema, the description should clarify what 'connection details' contains (URL, token, expiry) and any preconditions, and it does neither. For a gateway-connection tool this leaves a meaningful gap, though the core purpose is communicated adequately.

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 only one parameter (sandbox_id) and schema description coverage is 100%, so the schema already explains it. The description adds no extra meaning such as whether the sandbox must be awake or have an attached shell, so the high-coverage baseline of 3 applies.

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 ('Get') and a precise resource ('real-time bidirectional WebSocket PTY terminal gateway connection details'), so an agent knows this retrieves connection info rather than executing commands or listing sandboxes. It doesn't explicitly contrast itself with siblings like thanaton_exec_command or thanaton_attach_volume, but the resource is distinctive enough to separate it.

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?

The phrase 'for an attached interactive microVM shell' implies a prerequisite state (a shell must already be attached), but the description never says when to call this versus alternatives, nor what to do if no shell is attached. No explicit when-to-use or when-not-to-use guidance is present.

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