Skip to main content
Glama

List workspaces

list_workspaces
Read-onlyIdempotent

Retrieve Studio workspaces to see each workspace's storage location, which one is active, and any stale copy left by a storage move. Read-only JSON output with a configurable limit.

Instructions

List Studio workspaces. Use get_studio_entity with entity=workspaces for one workspace, and list_studio_catalogue for counts. On Studio 3.0 the storage key shows where each workspace lives, which one is active, and any stale copy left behind by a storage move. Read-only. Returns JSON items up to limit.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows. Integer from 1 to 500. Default 100.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
  2. Addedv6.1.5

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's 'Read-only' line is largely redundant. It does add useful non-annotation context, namely that on Studio 3.0 the storage key reveals where each workspace lives, which one is active, and stale copies left by a storage move, but it says nothing about ordering, pagination, or behavior on other Studio versions.

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?

Four sentences, front-loaded with purpose and sibling routing, with no filler. The closing 'Returns JSON items up to limit' is largely redundant given an output schema exists, which keeps it below a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only list tool with full schema coverage, rich annotations, and an output schema, the description covers purpose, alternatives, and the notable Studio 3.0 storage-key semantics. Nothing an agent needs to call it correctly 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 the single limit parameter already documents its range and default, so the schema carries the burden. The description only restates that results are returned 'up to limit' without adding format or semantics the schema lacks, which matches the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('List Studio workspaces') and immediately distinguishes the tool from two named siblings, one for a single workspace and one for counts. An agent can select it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent to get_studio_entity with entity=workspaces for a single workspace and to list_studio_catalogue for counts, giving clear conditions for the alternatives. It stops short of stating exclusions for this tool itself, such as that it offers no filtering or search, so a 4 rather than a 5.

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