Skip to main content
Glama
Purgatory (p7y)
by csakaszamok

list_runtimes

Read-only

List the runtimes available for new sandboxes, showing how each sandbox runs (dind, sysbox, kata) and the allowed runtime options.

Instructions

List the runtimes new sandboxes may use (how a sandbox runs: dind, sysbox, kata; ALLOWED_RUNTIMES) HTTP GET /runtimes

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": "list_runtimes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's marginal duty is small. It adds that the catalog is server-config driven (ALLOWED_RUNTIMES) and that it exposes an unfiltered HTTP GET /runtimes endpoint, but says nothing about whether the list is static per deployment or the shape of the returned entries beyond naming three examples.

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?

The core purpose is front-loaded in one compact sentence with the useful parenthetical immediately after. The trailing "HTTP GET /runtimes" is a little redundant given the empty schema but costs only a few words.

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 enumeration with no output schema, the definition covers what the values mean, where they come from (ALLOWED_RUNTIMES), and gives concrete examples. Only the exact return shape and whether the list can vary between calls is left unstated.

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 no parameter semantics to explain and the schema carries no burden. The description correctly signals that no filtering or scoping input is needed, matching the empty input 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?

"List the runtimes new sandboxes may use" gives a specific verb and resource, and the parenthetical (dind, sysbox, kata) plus ALLOWED_RUNTIMES makes clear what a "runtime" actually is. That is enough for an agent to distinguish it from the list_sandbox_* siblings, which all enumerate objects inside a sandbox rather than the runtime catalog.

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?

"runtimes new sandboxes may use" implies the tool is consulted before create_sandbox to pick a valid runtime value, but the connection is only implied. There is no explicit when-to-use statement, no when-not, and no named alternative, so the agent must infer the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.