Skip to main content
Glama

ctxstore — memory that follows you across models

List Workspaces

list_workspaces
Read-onlyIdempotent

The places this account's memory is organised into: its own projects (anything written under project::*, newest activity first), the workspaces other people have granted it (enter one with switch_workspace(name=)), and, for a sharer, who they invited and whether each person accepted and entered yet (shared_by_you). Shows which workspace this session is in, if any. Use it when a person's request is about one project, or asks who has access, or whether an invitee came in.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real context on top: the ordering of project results, the fact that grants belong to other people, and that the current session's workspace is reported if one exists.

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?

Every clause carries information and the usage sentence is clearly separated after the explanatory one. The first sentence is long and heavily parenthesised, so the core 'list workspaces' purpose is not front-loaded as sharply as it could be, but there is no filler.

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?

With no parameters, no output schema and full annotation coverage, the description carries the right amount of burden: it enumerates what comes back, its ordering, and the next action for entering a granted workspace. Exact field names and any size limits are left implicit, a minor gap for a zero-arg list tool.

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 no parameter semantics to add and the baseline is 4. The description correctly implies the tool is unfiltered — it returns all categories at once rather than being scoped by any argument.

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 names a specific resource and enumerates its distinct classes: own projects under project:<slug>:*, workspaces granted by others, and shared_by_you invite status. It also discloses ordering (newest activity first) and that the session's current workspace is flagged, so an agent knows exactly what it is asking for without opening a 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 gives explicit triggering conditions: when a request is about one project, asks who has access, or asks whether an invitee came in. It also names the follow-up action (switch_workspace(name=<grantor>)) for entering a granted workspace. No explicit when-not guidance, which keeps it just short of a 5.

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.