Skip to main content
Glama

List the Spaces the user holds a role in

spaces_list_spaces
Read-only

Return the user's Spaces with each one's id, kind (private, shared, or cohort: the Space of a workshop cohort the user is in), the user's role (owner, editor, or viewer), and how many notes, documents, and members it holds. Private comes first and belongs to the user alone.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a safe read (readOnlyHint true, destructiveHint false, openWorldHint false), so the bar is lower; the description still adds real value by explaining what comes back and by defining the enum values, including the non-obvious "cohort" kind and the owner/editor/viewer role set. It does not mention permissions, empty-result behavior, or whether counts are expensive, but with annotations covering the safety profile this is solid additional context.

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?

A single dense sentence that front-loads the return resource and then lists fields in a readable order. The parenthetical defining "cohort" is justified because that value is not self-explanatory; the closing note on Private ordering is brief and relevant. No filler sentences.

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 output schema, the description carries the burden of describing the return value, and it does so field by field, which is what an agent needs to plan downstream calls. Gaps are minor: it does not address pagination or result-size limits (likely none), nor what an empty list means for a new user.

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 the baseline is 4 and there is nothing for the description to compensate for. The schema is an empty object and the description correctly spends no space on arguments.

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 gives a specific verb and resource ("Return the user's Spaces") and enumerates exactly what each entry contains: id, kind, role, and note/document/member counts. It does not explicitly contrast itself with spaces_get_space or the other spaces_* siblings, so an agent must infer that this is the enumeration entry point, but the scope is otherwise unambiguous.

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 when-to-use or when-not-to-use guidance. Nothing tells the agent to call this first to discover space ids before using spaces_get_space or spaces_add_note, and no alternative is named. The only guidance-like sentence ("Private comes first and belongs to the user alone") is about result ordering and ownership, not tool selection.

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