List Pods
podsList workspace GPU/CPU containers or inspect a specific one by name, with live metrics, status, endpoints, and login details.
Instructions
List the pods (GPU/CPU containers) in a workspace, or show one pod by its pod_name (its display name also works).
workspace takes the id from the workspaces tool (a label also works); pass "all" to list pods across every workspace, or omit it if the user has only one.
Set include_metrics for live CPU/RAM/GPU usage of a single pod (ram_size, ephemeral_storage_* and GPU vram_size are MiB); use status to filter the list. System-managed downloader pods are hidden unless include_system is true; they are free and cannot be stopped or deleted.
To open a pod, use its endpoints (URLs; readiness ready/preparing/interrupted) and connect_credentials (logins the console shows on Connect, e.g. ComfyUI's ACCESS_PASSWORD). Secret values are null; set show_secrets with a single pod only when the user asks for the login (a read-only API key gets "***").
Each endpoint's access says who can reach it: internal (only from inside the workspace), locked (only workspace members signed in to the console and requests that carry one of the port's access keys) or unlocked (anyone who knows the URL). A locked port answers a request without a key with 401 and sends a browser to the console to sign in. That is the lock working, not a fault: don't restart, edit or delete the pod for it. To call the app for your own work, use run_command inside the pod against http://localhost:; for a program outside the pod, ask the user whether to create an access key (create_access_key). set_port_lock locks or unlocks a port. A lock choice takes a few seconds to take effect: an endpoint's lock_state is locking or unlocking until then (else locked or unlocked, null when the server doesn't say), and a locking port can still be reached without a key. locked is the choice itself. allow_preflight true means CORS preflight requests (OPTIONS) reach the app without a key while the port is locked (set_port_preflight).
A stopped pod's stop_reason_code (other than "user") says the system stopped it, and same_node_unavailable_reason why it cannot start on its machine now.
restart_count and last_exit (one pod: recent_exits, current_run marks this run) say whether its main container keeps ending and why; status can stay running meanwhile.
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": "pods"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pod | No | ||
| limit | No | ||
| cursor | No | ||
| status | No | ||
| workspace | No | ||
| show_secrets | No | ||
| include_system | No | ||
| include_metrics | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||