Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resume service

service_resume
DestructiveIdempotent

Resume a paused Lizard app or database to restore it with the same image, URL, host, port, password, settings, and data. Use it to bring a stopped service back online without reconfiguring.

Instructions

Use this when the user wants to start a paused Lizard service (app or database) again. It comes back from the same image with the same URL, host, port, password, settings and data. Pausing or resuming one that already is does nothing.

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_resume"
  }
}

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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=true, so the description doesn't need to restate safety. It does add real context beyond them: the service returns with the same image, URL, host, port, password, settings and data, and the no-op behavior reinforces the idempotency hint. It doesn't cover permissions or side effects like billing changes.

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?

Three short sentences, front-loaded with the usage trigger, then what the agent gets back, then an edge case. Every sentence earns its place, though the final clause is slightly awkwardly worded.

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 two-parameter tool with full schema coverage and annotations covering safety, the description supplies the missing behavioral picture: state preservation and idempotency. No output schema exists, but the 'it comes back with the same ...' sentence effectively communicates what to expect, so only minor gaps remain.

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% and both parameters are documented, so baseline is 3. The description's mention of 'app or database' restates what the service schema already says and adds no new syntax or format guidance for project or service.

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 ('start a paused Lizard service (app or database) again'), which is clearly distinct from service_pause and from workspace_resume. An agent can identify the operation without opening the schema.

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?

The opening sentence gives a clear trigger condition: the user wants to start a paused service again. The closing sentence adds that pausing/resuming an already-satisfied target is a no-op, which further pins down when calling is meaningful. It stops short of naming sibling alternatives explicitly (e.g., service_pause, project_resume).

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