Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Query Workspaces

query_workspaces

Search workspaces by name or query string to filter and locate the relevant Cutover workspace for your cutover operations.

Instructions

Search for workspaces by name or query string.

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": {
      "query": "<query>"
    },
    "name": "query_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe search string to filter workspaces by.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

There are no annotations, so the description carries the entire behavioral burden. It does not disclose match semantics (substring vs. exact, case sensitivity), result limits, pagination, or whether searches are scoped to the caller's organization. For a search tool, these omissions are significant.

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?

One short, front-loaded sentence with no filler. It is not padded, although its brevity reflects under-specification rather than disciplined economy.

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?

The tool is simple, the input schema is fully documented, and an output schema exists, so the return values need not be explained. However, with no annotations and no sibling differentiation, the definition leaves the agent guessing about matching behavior and when to prefer this tool over 'list_workspaces'.

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 single 'query' parameter is fully documented in the schema. The description's phrase 'by name or query string' adds marginal meaning about what fields are matched, which is not obvious from the schema alone, so a baseline 3 applies.

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 and resource: 'Search for workspaces'. It is unambiguous on its own, but it does not distinguish this tool from the sibling 'list_workspaces' or explain how it differs from 'get_workspace_by_id'.

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 guidance on when to use this tool versus 'list_workspaces' (unfiltered listing) or 'get_workspace_by_id' (single lookup). The description gives no exclusions, prerequisites, or context that would help an agent choose among these sibling tools.

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