Skip to main content
Glama
flowsery

flowsery

Official

List Workspaces

list_workspaces
Read-onlyIdempotent

Lists every workspace a sign-in can act in, with IDs, roles and permissions. Use it to find the right workspaceId when a user names a workspace, client or organization, or when expected data is missing.

Instructions

List the workspaces this sign-in can act in, across every organization the user belongs to. Returns { status, data } with one entry per workspace: id, name, organization { id, name }, role { key, name }, permissions, isDefault and current. Call this when the user names a workspace, client or organization, or when data they expect is missing, then pass the matching id as workspaceId to every other tool. Without workspaceId, tools act in the workspace marked current. A workspace API token (flow_ws_) belongs to one workspace, so it lists only that one; a website key (flow_) belongs to one website and fails with a 400 here. Takes no arguments.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds behavior the annotations cannot convey: credential-dependent scope (a flow_ws_ token sees only its own workspace, a flow_ key fails with a 400) and the cross-tool consequence of omitting workspaceId. That is meaningful added context rather than restatement.

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?

Three tight sentences, front-loaded with purpose before usage and credential caveats. The enumeration of return fields (id, name, organization, role, permissions, isDefault, current) partially duplicates the existing output schema and could be trimmed without losing agent-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool it covers everything an agent needs: what it returns, when to call it, how to use the result downstream, the default when no workspace is chosen, and which credential types behave differently. Nothing material is left to inference.

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?

With zero parameters the baseline is 4, and the description goes a step further by stating 'Takes no arguments' and explaining that this tool is the source of the workspaceId value consumed by other tools. That clarifies the parameter's origin even though this schema has none.

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?

Opens with a specific verb and resource plus its scope: 'List the workspaces this sign-in can act in, across every organization the user belongs to.' That scope statement clearly separates it from siblings like list_websites and list_issues, so an agent can identify the tool without opening its schema.

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 explicit triggering conditions ('when the user names a workspace, client or organization, or when data they expect is missing') and an explicit follow-up action: pass the matching id as workspaceId to every other tool. It also states the fallback when no workspaceId is supplied, which tells the agent when this call is optional.

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