Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Create Workspace

create_workspace

Creates a new Cutover account/workspace with a required name and key, plus an optional description.

Instructions

Create a new account/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": {
      "name": "<name>",
      "key": "<key>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesRequired, shortened version of the workspace/account name.
nameYesThe name of the new workspace/account.
descriptionNoAn optional description for the workspace/account.

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 only restates that creation happens. It says nothing about permissions required, what happens on a duplicate key, whether creation is reversible, or any side effects — all critical for a mutation tool with zero annotation coverage.

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?

It is a single short sentence with no wasted words, so it is maximally concise. But the brevity reflects under-specification rather than economy, and the 'account/workspace' slash construction introduces ambiguity instead of clarity.

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, but for a create/mutation tool with no annotations the description is far too thin. It omits duplicate-key behavior, permission requirements, and the account-versus-workspace relationship that the parameters imply.

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 all three parameters are already documented in the schema, which sets the baseline at 3. The description adds no extra meaning about the 'key' uniqueness/format constraint or how name and key relate, so it does not exceed that baseline.

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?

The description names a specific verb and resource ("Create a new ... workspace"), so the basic action is legible. However, the "account/workspace" hedge leaves it unclear whether one or two entities are created, and it does nothing to distinguish this from siblings such as get_workspace_by_id or the various create_* tools.

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 prerequisites, and no mention of alternatives or when not to call it. An agent must infer entirely from the tool name that this is the entry point for provisioning a workspace.

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