Skip to main content
Glama

signvoy_list_workspaces

Read-only

List all workspaces the authenticated user belongs to. Returns id, name, slug, role, and personal flag. Use the returned id as workspace_id in other tools. Call this first when starting any workflow, unless you already know the user has a single workspace — every other tool refuses to guess between several and fails with an ambiguous-workspace error. When more than one comes back, ask the user which they mean rather than picking for them.

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": "signvoy_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds real behavioral context beyond that: the downstream failure mode of ambiguous workspace resolution and the expected disambiguation behavior. It also discloses the shape of the result (id, name, slug, role, personal flag) even though no output schema exists.

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 sentences, each carrying distinct information: what it returns, how to use the result, and when to call it plus the disambiguation rule. The routing guidance and the exception are front-loaded rather than buried, and there is no filler.

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-only discovery tool with no output schema, the description supplies everything an agent needs: the return fields, the workflow ordering, the ambiguous-workspace failure mode, and user-facing disambiguation behavior. 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?

The tool takes zero parameters, so the baseline is 4 and no input semantics are needed. The description's note about reusing the returned id as workspace_id in other tools is useful linkage but pertains to outputs rather than this tool's inputs.

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 all workspaces the authenticated user belongs to') and immediately enumerates the returned fields (id, name, slug, role, personal flag). This distinguishes it cleanly from the sibling list_* tools, which target contacts, documents, and templates rather than the workspace container itself.

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?

Explicitly prescribes when to call it ('first when starting any workflow'), carves out the exception ('unless you already know the user has a single workspace'), and explains the consequence of skipping it (other tools fail with an ambiguous-workspace error). It also gives a decision rule for multi-result cases: ask the user rather than guessing.

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