Skip to main content
Glama

List Workspaces

list_workspaces
Read-onlyIdempotent

List workspaces the caller can access.

The personal workspace (is_personal: true) is listed first. Pass a workspace_id from this list to target a specific workspace. check_credits requires one; create tools such as onboard_brand may default to the personal workspace when their own docs say workspace_id is optional.

Args: (none)

Returns: { "workspaces": [ { "workspace_id": string | null, "workspace_name": string, "is_personal": boolean, "pricing_version": number } ] }

The caller's personal workspace (auto-created at signup) is listed first and tagged "is_personal": true.

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
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
workspacesYesWorkspaces the caller can access, personal workspace first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description rightly spends its words elsewhere: ordering guarantees (personal workspace first, tagged is_personal), the fact that personal workspaces are auto-created at signup, and the workspace_id:null possibility. That ordering contract is behavior an agent cannot get from annotations or schema.

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?

Front-loaded with purpose, then usage, then return shape. It loses a point because the 'personal workspace is listed first and tagged is_personal:true' fact is stated twice (top paragraph and closing sentence), which is avoidable repetition.

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 zero-required-argument read tool with rich annotations and an output schema, nothing an agent needs is missing: purpose, ordering contract, follow-up usage, and the return shape are all present. It is arguably over-complete rather than under-complete.

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?

The lone llm_model parameter is fully documented in the schema (100% coverage), so the schema carries the semantics; the description adds nothing about it, and its 'Args: (none)' line is mildly at odds with the presence of an optional analytics parameter. Baseline 3 applies when schema coverage is complete.

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 workspaces the caller can access') and scopes it to the caller's access, which cleanly separates it from the many other list_* siblings. An agent knows exactly what it gets back without further reading.

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 tells the agent how the result is consumed: pass a workspace_id to target a workspace, check_credits requires one, and create-onboarding tools may default to personal. That is strong downstream guidance, though it never states a precondition such as 'call this first if you don't already have a workspace_id', and gives no explicit when-not/exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources