Skip to main content
Glama

thanaton_list_sandboxes

List active, sleeping, and managed MicroVM sandboxes across the current tenant to monitor sandbox state and maintain an accurate inventory.

Instructions

List all active, sleeping, and managed MicroVM sandboxes across the current tenant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thanaton_list_sandboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/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 burden. 'List' implies a read-only, non-destructive operation, and 'across the current tenant' usefully hints that tenant scoping comes from ambient auth rather than a parameter. It says nothing about pagination, result volume, or how the three lifecycle states are represented in the response.

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 front-loaded sentence with no filler. The state enumeration and tenant scope are packed into one clause and nothing is redundant.

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 zero-parameter, read-only listing call with no output schema, the description covers what is needed to select and invoke it. The only real gap is the absence of any note on return volume or ordering, minor for a tool this simple.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond confirming scope. The mention of 'current tenant' adds the one meaningful semantic point — that no tenant identifier is needed — which is the correct baseline for a parameterless tool.

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 pairs a specific verb (List) with a specific resource (MicroVM sandboxes) and states the scope: the current tenant. It implicitly separates this read tool from the sandbox lifecycle siblings (spawn, sleep, destroy), but it never names an alternative listing tool or clarifies how it relates to them.

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: an agent can infer this is the discovery call before spawn/sleep/destroy operations. There is no explicit when-to-use statement, no when-not-to-use, and no mention of prerequisites such as an authenticated tenant context that the 'current tenant' phrasing depends on.

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