Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

List Folders

list_folders

Fetch all folders in a specified Cutover workspace by workspace_id, enabling users to inspect and manage the workspace folder structure.

Instructions

List all folders in a specific workspace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe unique identifier for the workspace.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYesTop-level metadata for a list response.
linksYesPagination links for a list response.
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about this being a read-only operation, whether results are paginated, how folders are ordered, or whether nested/subfolders are included ("all folders" is ambiguous on hierarchy). The presence of an output schema relieves it of explaining return shape, but the operational behavior remains undisclosed.

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?

A single front-loaded sentence with no filler or redundancy. It is appropriately sized for a one-parameter listing tool, though it is so terse that it borders on under-specification rather than efficient communication.

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

Completeness3/5

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

For a simple one-parameter read tool with a full output schema, the definition covers the essential who/what. However, with zero annotations it should compensate with at least a note on read-only behavior, pagination, or folder hierarchy, none of which appear.

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 coverage is 100% and the sole parameter is fully documented in the schema, so the baseline is 3. The description's phrase "in a specific workspace" reinforces the scoping relationship but adds no syntax, format, or constraint detail beyond the schema.

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?

The description names a specific verb ("List") and resource ("folders") and scopes it to "a specific workspace," which is unambiguous. It does not name or distinguish itself from related listing tools such as list_workspaces or list_streams, but the resource noun is distinct enough that confusion is unlikely.

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 explicit when-to-use guidance, no statement of prerequisites (e.g., that the workspace must exist or that permissions are required), and no mention of alternatives. The only implied usage cue is that a workspace_id must be supplied, which the schema already enforces.

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