Skip to main content
Glama

list_workspaces

Retrieve all MindGate project workspaces with their memory counts to review available projects and understand stored context.

Instructions

List all project workspaces stored in MindGate along with memory counts.

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 observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral load: "List" implies a read-only operation, which is useful but not explicit. It does not disclose ordering, pagination, whether empty or archived workspaces are included, or any permission/scope requirements, so meaningful gaps remain for a zero-annotation tool.

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?

A single sentence with the action front-loaded and no filler. Every clause (what is listed, where it lives, what is attached) contributes information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only source of return-shape information, and it goes only as far as "workspaces with memory counts" without indicating what identifies a workspace (name, ID) or whether the result is a collection with any nesting. For a simple zero-param read tool this is adequate but not fully complete.

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 no parameters, so there is no parameter semantics to add; the baseline for zero-param tools applies. The description correctly avoids inventing filters or options that the empty schema would contradict.

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?

"List all project workspaces stored in MindGate" gives a specific verb and resource, and the added "along with memory counts" clarifies what each entry carries. No sibling in the catalog does workspace enumeration, so it is distinguishable, though it never explicitly contrasts itself with related read tools like recall_context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus alternatives, no prerequisite context (e.g., whether a workspace must exist first), and no guidance on whether it should precede other workspace-scoped calls. The discovery use case is only inferable from the name and the mention of memory counts.

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