Skip to main content
Glama

List workspaces

clipember_list_workspaces
Read-onlyIdempotent

Show the team workspaces the user belongs to — their personal one plus any they were invited to — with their role (admin or member), member count and which one is current. In the current workspace every tool works with that team's shared accounts, posts and media, on the owner's plan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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's job is to add semantics — and it does, by defining what 'current workspace' means for downstream tool behavior (shared accounts, posts, media, owner's plan). It also discloses the contents of each record in lieu of an output schema, though it says nothing about ordering or completeness of the list.

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 sentences, front-loaded with the resource and its returned fields before the scoping explanation. The second sentence is somewhat dense and mixes two ideas (workspace scoping and plan ownership), but no sentence is filler.

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?

With no parameters and no output schema, the description carries the full burden of describing the response, and it does so by naming the exact per-workspace fields (role, member count, current flag) plus the personal-plus-invited scope. Nothing an agent needs in order to call and interpret this tool 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, so there is nothing to disambiguate and the baseline is 4. The description correctly implies a no-argument call by describing the result as 'the workspaces the user belongs to' with no filtering input.

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 gives a specific verb (show) and resource (team workspaces), and enumerates the returned attributes: role (admin or member), member count, and which workspace is current. It is clearly distinct from clipember_list_workspace_members, which lists people inside a workspace rather than workspaces themselves.

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 implied rather than stated: the second sentence explains that the current workspace scopes every other tool, which hints at why an agent would call this first, but there is no explicit 'use this when…' or any named alternative to route away from. An agent can infer the entry-point role but must do the reasoning itself.

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