Skip to main content
Glama

list_spaces

List spaces, group chats, and DMs sorted by recent activity to help AI agents find conversations. Use page size to paginate results.

Instructions

List spaces, group chats and DMs, most recently active first.

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_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. Beyond the sort order it says nothing about read-only safety, auth/workspace requirements, result limits, or how to continue past the first page — and since the schema offers page_size but no cursor or token, an agent cannot tell how to paginate.

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 front-loaded sentence with no filler, which suits a simple list tool. It is arguably too terse, but nothing written is wasteful or poorly ordered.

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?

An output schema exists, so return values needn't be explained, and a one-parameter list tool is not inherently complex. Still, with zero annotations and no pagination semantics anywhere, an agent lacks enough to invoke this repeatedly or know its scope limits, leaving the definition only minimally viable.

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

Parameters2/5

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

Schema description coverage is 0% for the single page_size parameter, and the description says nothing about it — no default behavior, no maximum, no interaction with paging. The one parameter is simple and self-describing by name, but the description fails to compensate for the documentation gap it should fill.

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?

States a specific verb and resource ('List spaces') and expands the scope to include group chats and DMs, which tells an agent what content comes back. It does not name or contrast itself with any sibling such as list_unread or search_messages, so sibling differentiation is left to inference.

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 and no mention of alternatives for finding conversations. The ordering note ('most recently active first') is the only usage-shaped information, and it does not tell an agent when browsing this list is preferable to searching or reading unread items.

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