Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Workspace By Id

get_workspace_by_id

Retrieve details for a specific Cutover workspace by its unique ID. Use it to inspect workspace metadata and configuration when you know the workspace identifier.

Instructions

Fetch details for a specific workspace by its ID.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe unique identifier for the workspace.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It provides no context on error handling (e.g., what happens if the ID is not found) or safety (read-only nature).

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?

The definition is a concise, single sentence that perfectly communicates the tool's function without any unnecessary wording or fluff.

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?

While the schema is complete for the parameter, the description lacks crucial contextual completeness for a simple lookup tool, such as expectations regarding response structure or error states beyond the basics.

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?

Since schema description coverage is 100%, the baseline score is 3. The description merely restates the concept of a 'specific' ID, adding no meaningful semantic information beyond what the schema provides.

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 uses a clear verb ('Fetch details') and identifies the resource ('workspace') and the method ('by its ID'). While it is clear, it does not explicitly contrast this with sibling methods like searching or listing workspaces.

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?

The definition offers no guidance on when or why to use this tool over alternatives (e.g., if the ID is guaranteed to be valid, or if filtering is possible). It is purely descriptive.

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