Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

List Workspaces

list_workspaces

Retrieve a paginated list of all workspaces, using limit and offset to control how many results are returned and skipped.

Instructions

List all workspaces.

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
limitNoThe maximum number of workspaces to return.
offsetNoThe number of workspaces to skip from the beginning.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about authorization requirements, result ordering, or the fact that results are paged. The word "all" is also mildly at odds with the default limit of 50, which could lead an agent to assume an unbounded result set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted clauses, so it is front-loaded, but it is under-specified rather than concise. Nothing in it earns a place beyond the tool name itself.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and the input schema is fully described. But with zero annotations and a thin description, an agent gets no signal on safety, pagination expectations, or how this differs from query_workspaces, leaving the definition incomplete for a read-listing tool with a same-domain sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so limit and offset are already fully documented in the schema with defaults. The description adds no meaning beyond that, which matches the baseline of 3 when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List all workspaces" gives a clear verb and resource, but it essentially restates the tool name/title and adds only the word "all". It draws no line between this tool and the sibling query_workspaces, so an agent cannot tell from the description which one is the enumeration endpoint versus the filtered search.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer query_workspaces, and no stated prerequisites such as permissions or scope. The agent is left to infer usage entirely from the name.

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