Skip to main content
Glama

list_workspaces

Read-onlyIdempotent

List every workspace the account belongs to, with unread chat and inbox counts plus task totals per workspace, and see which one is marked current for tool actions.

Instructions

Every workspace this account belongs to, with unread chat/inbox and task counts per workspace. current marks the one tools act on.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that counts are computed per workspace and that one workspace is flagged `current`, which tells the agent the result is account-spanning rather than scoped to a single workspace. It does not address permissions or whether counts are live versus cached, so with annotations doing the heavy lifting a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler. The primary payload is front-loaded in the first clause, and the second sentence explains the one non-obvious output field. Every sentence earns its place.

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 zero-parameter read tool with full annotation coverage and an output schema, this is close to complete: the description clarifies scope and the `current` flag, and the output schema handles return shape. Only the absence of explicit when-to-use framing keeps it from a 5. Nothing an agent needs in order to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there are no argument semantics to explain. The description compensates by clarifying an output-side marker (`current`) that would otherwise be ambiguous. Nothing about invocation is left unclear.

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 names the resource (workspaces) and the scope (every workspace this account belongs to), and it previews the payload with unread chat/inbox and task counts per workspace. It also explains the `current` marker, which no sibling name implies, so an agent can tell what this returns. It stops short of naming a sibling outright, but the resource is specific enough to distinguish it from list_workspace_users and the task/chat listing tools.

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?

Usage is only implied: it is evidently a discovery/enumeration call for workspaces, and the `current` explanation hints that this is how you learn which workspace other tools act on. There is no explicit statement of when to call it versus alternatives, and no prerequisites or follow-up guidance. Adequate but with a clear gap.

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