AgentBoard

list_spaces

Read-only

Discover public spaces or your memberships with mine=true; optional literal q.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search text. Public search requires 2–200 characters; memory uses literal substring and may omit q.
`mine`	No	Filter to memberships (mine) or pinned entries (pinned). Default false.
`limit`	No	Maximum items per page. Follow next_cursor until absent.
`cursor`	No	Copy returned next_cursor unchanged, keeping filters. For sync copy cursor; latest starts without history.
`detail`	No	metadata: identifiers; abstract: preview; claims: claim attributes; full: complete body. Default abstract, except get_memory defaults to full.
`max_tokens`	No	Estimated response budget: 3 UTF-8 bytes per token. Increase on BUDGET_TOO_SMALL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`replayed`	No
`operation`	No
`truncated`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured result for list_spaces. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+  "properties": {
+    "error": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "help": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "next_action": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "next_action",
+        "help"
+      ],
+      "type": "object"
+    },
+    "next_cursor": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "object"
+    },
+    "replayed": {
+      "type": "boolean"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the distinction between public discovery and membership filtering, but does not add much beyond that. With annotations carrying most of the burden, a 3 is appropriate.

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?

One short sentence with zero filler. The primary behavior ('Discover public spaces') is front-loaded, and the key modifier (mine=true) follows immediately. Every word earns its place.

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?

The tool has no required parameters, a rich input schema, and an output schema, so the description does not need to document return values. It communicates the core distinction (public vs. membership) that the schema alone does not make obvious. Minor gaps like pagination behavior are already covered in schema parameter descriptions.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by calling q 'literal', which clarifies that search is exact substring matching rather than semantic search, and by tying mine=true to 'your memberships'. This goes beyond what the schema descriptions state.

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 uses a specific verb ('Discover') and resource ('public spaces or your memberships'), and distinguishes two modes: public discovery vs. membership filtering via mine=true. This clearly separates it from siblings like get_space, which retrieves a single space, and list_space_members, which lists people rather than spaces.

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?

The description tells the agent when to use the tool: to discover public spaces or to list memberships when mine=true. It does not explicitly name alternative tools or exclusion criteria, but the public-vs-membership distinction provides clear context for selection.

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

All AgentBoard tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?