Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pause service

service_pause
DestructiveIdempotent

Pause a Lizard app or database by scaling it to 0 to stop serving requests and refuse connections while keeping settings, volumes, and endpoints; no compute billing. Resume later.

Instructions

Use this when the user wants to stop a Lizard service (app or database) without deleting it: it scales to 0, its URL answers 503 and a database refuses connections. Its URL, database host, port, password, settings and volumes are all kept, and nothing is billed for compute while paused. Undo with service_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>",
      "service": "<service>"
    },
    "name": "service_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject name, slug, or ID
serviceYesApp or database name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Excellent disclosure of observable consequences the annotations cannot convey: scale-to-0, URL returns 503, database refuses connections, and URL/host/port/password/settings/volumes are preserved with no compute billing. One gap: annotations set destructiveHint=true while the description emphasizes nothing is lost and the action is fully reversible; the description never reconciles why this is flagged destructive, which could leave an agent unsure how much caution to apply.

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?

Two tight sentences, front-loaded with the triggering condition, then the behavioral effects and the undo path. No filler and no repetition of the title.

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 two-parameter, no-output-schema state-change tool, the description covers trigger, effects, resource retention, billing, and reversal. Nothing an agent needs in order to call it correctly is missing.

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% with only two required params (project, service), each already documented in the schema as accepting name/slug/ID. The description adds no parameter guidance beyond what the schema provides, 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 (pause/stop) and resource (Lizard service, app or database), and explicitly separates itself from deletion ('without deleting it'), which is the key confusion against service_delete. It also names service_resume as the inverse, so an agent can distinguish it from every nearby sibling.

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 ('when the user wants to stop a Lizard service... without deleting it') and an explicit undo path ('Undo with service_resume'), plus the implications of pausing in concrete terms. The alternative (delete) and the reversal are both spelled out, leaving nothing to inference.

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