Skip to main content
Glama

workspace_list

Read-onlyIdempotent

List your isolated workspaces on a fleet to retrieve each one's id, runner, session, image, state, and timestamps. Use it to inspect or audit active sandboxes.

Instructions

List your own workspaces (isolated sandboxes) on a fleet: id, runner, session, image, state and times.

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

Input Schema

NameRequiredDescriptionDefault
fleetNoFleet name. Omit to use the default.
contextNoContext name. Omit to use the default.

Output Schema

NameRequiredDescriptionDefault
whereYes
truncatedYes
workspacesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered elsewhere. The description adds useful scope ('your own' sandboxes) and the shape of what is returned, but says nothing about ordering, pagination, or what an empty result means. Adequate but thin beyond the annotations.

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 the action first and the field list after; no filler. The parenthetical 'isolated sandboxes' earns its place by disambiguating what a workspace is.

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?

An output schema exists, so return values need no prose explanation, and annotations carry the safety semantics. The description covers purpose and scope for a simple two-optional-parameter list tool; only cross-tool routing guidance is missing.

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?

Schema coverage is 100%, and both parameters (fleet, context) already document their default-on-omit behavior in the schema. The description's phrase 'on a fleet' loosely maps to the fleet parameter but adds no syntax or format detail beyond the schema, so the 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?

Names a specific verb (list) and resource (workspaces / isolated sandboxes), scopes it to the caller's own workspaces on a fleet, and enumerates the returned fields. It is clearly distinguishable from job_list, list_fleets and list_runners by the 'workspace' resource, though it never names a sibling to contrast with.

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?

There is no explicit when-to-use or when-not-to-use guidance; the only implicit signal is 'your own workspaces', which tells the agent it is not a cross-user listing. Nothing routes the agent between this and workspace_open/workspace_close or the fleet/runner listing tools.

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