Skip to main content
Glama

List Spaces Tool

list-spaces
Read-onlyIdempotent

Returns the spaces this token is bound to. Each space includes slug, display_name, and the caller's user_role. Call this before other tools. When more than one space is returned, pass slug as space on later tools.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuine value beyond that: it discloses the credential-scoping behavior ('this token is bound to') and the shape of each returned record, which annotations cannot express. It does not address the empty-result case or ordering, keeping it short of a 5.

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?

Three short sentences, front-loaded with the purpose, then the return shape, then the workflow instruction. No filler, no restatement of the title, and the most actionable guidance sits early.

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 and no output schema, the description correctly compensates by naming the returned fields, which is exactly what an agent needs to consume the result. The remaining omission is edge-case behavior (zero spaces, multiple spaces' ordering), a minor gap for a simple read 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 the baseline is 4. The only parameter-adjacent statement concerns other tools (passing slug as the 'space' argument downstream), which is helpful context rather than a gap.

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?

States a specific verb and resource ('Returns the spaces this token is bound to') and immediately enumerates what each space contains (slug, display_name, user_role). It is unmistakably a discovery/enumeration tool, distinguishable from siblings like list-datasets or get-dataset-metadata.

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

Usage Guidelines5/5

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

Gives an explicit sequencing instruction ('Call this before other tools') plus the conditional hand-off rule ('When more than one space is returned, pass slug as space on later tools'). That is both a when-to-use and a what-to-do-next directive, leaving little to inference.

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