Skip to main content
Glama

List workspaces

list_workspaces
Read-only

List workspaces an authenticated user can access, with optional name or name-prefix filters to find the right workspace.

Instructions

Lists the workspaces the authenticated user can access. Optionally filter by name.

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
nameContainsNoOnly workspaces whose name contains this (case-insensitive).
nameStartsWithNoOnly workspaces whose name starts with this (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description usefully adds that results are limited to workspaces the caller can access, but it says nothing about result ordering, pagination, or empty-result behavior for a list operation.

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?

Two compact sentences with the primary purpose front-loaded and no filler. Nothing is wasted, though it is minimal rather than maximally informative.

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 simple read-only listing tool with a fully documented two-parameter schema and a readOnly annotation, the description covers what the tool does and its auth scope. Missing pagination or ordering notes are minor given the tool's simplicity and lack of an output schema.

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 are fully documented in the schema, including case-insensitivity. The description's 'filter by name' overlaps with the schema without adding format or precedence details, so the baseline 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?

The description states a specific verb and resource ('Lists the workspaces') and adds a meaningful scope qualifier ('the authenticated user can access'), so an agent can distinguish it from write siblings like create_workspace or delete_workspace. It doesn't explicitly contrast with other list_* tools, but the resource noun is unambiguous.

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?

The scope note about accessible workspaces implies when the tool applies, and 'Optionally filter by name' indicates filtering is discretionary. However, there is no explicit when-to-use/when-not guidance and no mention of an alternative for finding workspaces by other criteria.

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