Skip to main content
Glama

List workspaces

list_workspaces

Retrieve your account's workspaces to find the workspaceId needed for filtering monitors or creating a monitor in a team workspace instead of the key owner's personal workspace.

Instructions

List the account's workspaces (business accounts hold several; personal accounts have one). Use this to find the workspaceId to filter list_monitors by, or to create a monitor into a team workspace instead of the key owner's personal one.

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 observedv0.5.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully explains the account-scoping behavior (results are the account's workspaces, with count depending on account type), but says nothing about ordering, pagination, or required permissions/scope for the read.

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?

Two sentences, front-loaded with the core action and followed by the concrete use case. No filler or restatement of the title.

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 zero-parameter read with no output schema, the description covers what an agent needs: what is returned conceptually and why it would call it. It could go slightly further by noting the fields on a workspace (e.g., id and name) or that all workspaces are returned in one call.

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 nothing for the description to disambiguate; baseline 4 applies. The mention of workspaceId as the output value an agent will need is a helpful touch even though no parameter exists.

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 ("List the account's workspaces") and immediately clarifies cardinality semantics: several for business accounts, one for personal accounts. This lets an agent distinguish it from sibling list_* tools that enumerate other resources.

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 concrete when-to-use guidance: to obtain a workspaceId for filtering list_monitors, or to target a team workspace when calling create_monitor instead of the key owner's personal workspace. It names the downstream tools but does not state any exclusion or prerequisite, so it falls just short of a full 5.

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