Skip to main content
Glama

list_workspaces

Read-onlyIdempotent

Lista los workspaces del usuario, con su rol y configuración. Con token sb_* retorna solo el workspace vinculado al token. Sirve para conseguir el workspace_id cuando no se conoce.

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 observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: with an 'sb_*' token the result set is narrowed to the token's single linked workspace, which changes how the agent must interpret an empty or single-item response. Pagination/ordering behavior is not mentioned.

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 what is listed and what it returns, then the token-scoping caveat, then the use case. Nothing is redundant and nothing repeats the annotations.

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?

For a simple no-param read with no output schema, the description covers what is returned (workspaces with role and configuration), the token-scoping exception, and the discovery use case — enough to call it correctly. Minor absences like ordering or whether all memberships are included are not blocking.

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 there is no parameter meaning for the description to carry; the schema and description are consistent. Baseline for a 0-param tool applies with no gaps to compensate for.

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 ('Lista los workspaces del usuario') plus what each entry carries (rol y configuración), so the agent knows exactly what comes back. It does not explicitly contrast with the nearest sibling (configurar_workspace), so it stops short of full sibling differentiation.

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?

Gives a concrete use case — 'Sirve para conseguir el workspace_id cuando no se conoce' — which tells the agent when this tool is the right call. It offers no explicit exclusions or named alternatives, but for a zero-parameter discovery tool the positive guidance is clear.

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