Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pause workspace

workspace_pause
DestructiveIdempotent

Stops all services across every project in a workspace without deleting data, letting owners halt activity while preserving state. Resume the workspace to undo.

Instructions

Use this when the workspace owner wants to stop every service in every project of a workspace without deleting anything (same as project_pause for each project). Owner only. Undo with workspace_resume.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "workspace_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID (see workspace_list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety profile is largely covered. The description adds what annotations cannot: the owner-only permission requirement, the blast radius (all services in all projects), and the reversibility path via workspace_resume. It does not mention effects on in-flight traffic or whether individual services need re-resume.

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?

Effectively two short sentences: the trigger and scope first, then auth and undo. The parenthetical equating it to project_pause is the most information-dense clause and nothing is redundant.

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

Completeness4/5

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

For a single-parameter mutation with no output schema and full annotation coverage, the description supplies scope, permissions, and the undo tool. Only the post-call state of paused services (do they remain paused indefinitely, are they resumable individually) is left implicit.

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?

Only one parameter and the schema already documents workspaceId at 100% coverage, including the workspace_list pointer. The description adds no format or sourcing detail beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb (stop) and resource (every service in every project of a workspace), and explicitly equates it to project_pause applied per project. This clearly separates it from project_pause, service_pause, and workspace_delete in the sibling list.

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

Usage Guidelines5/5

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

Gives an explicit trigger (owner wants to stop all services across the workspace), an explicit exclusion versus the delete siblings ("without deleting anything"), and names the inverse tool (workspace_resume). An agent can route between pause/resume/delete without opening any schema.

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

Deploy Server

Other Tools