Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pause project

project_pause
DestructiveIdempotent

Stop all services in a Lizard project without deletion: scales apps and databases to zero, retains URLs, ports, passwords, settings, volumes, and reports paused/skipped items; resume later.

Instructions

Use this when the user wants to stop every service of a Lizard project without deleting anything: each app and database scales to 0, keeping its URL, host, port, password, settings and volumes. Returns what was paused and what was skipped, with why. Undo with project_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": {
      "project": "<project>"
    },
    "name": "project_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject name, slug, or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by enumerating exactly what is preserved (URL, host, port, password, settings, volumes) and by disclosing that the result is partial-success aware ("what was paused and what was skipped, with why"). It adds real context to destructiveHint=true without contradicting it — scaling to 0 is disruptive but not data-destroying.

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?

Three tight sentences, front-loaded with the trigger condition, then effect, then return semantics, then undo path. No sentence is filler.

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

Completeness5/5

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

For a one-parameter mutation with no output schema, the description covers trigger, effect, persistence guarantees, return shape, and undo path. An agent has everything needed to call it correctly and to explain the outcome to a user.

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% for the single `project` parameter, so the schema already carries the meaning. The description refers to "a Lizard project" but adds no format or scoping detail beyond what the schema states, so 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 and resource ("stop every service of a Lizard project") plus the crucial scope qualifier "without deleting anything," which distinguishes it from project_delete. The mechanism ("each app and database scales to 0") makes the effect concrete rather than a restatement of the name.

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

Usage Guidelines4/5

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

"Use this when the user wants to stop every service... without deleting anything" gives an explicit trigger condition, and "Undo with project_resume" names the reverse action. It does not explicitly route to service_pause for single-service stopping, which is the main remaining ambiguity in a very crowded sibling set.

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