Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resume project

project_resume
DestructiveIdempotent

Resume paused services for a Lizard project and report which services restarted or were skipped, including why (billing-frozen services stay paused until paid).

Instructions

Use this when the user wants to start again the services of a Lizard project that they paused. Services paused by a billing freeze stay paused until the account is paid. Returns what was resumed and what was skipped, with why.

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

Input Schema

NameRequiredDescriptionDefault
projectYesProject name, slug, or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the billing-freeze exception and the return shape ('what was resumed and what was skipped, with why'), which is genuine partial-success behavior an agent needs. It does not explain why destructiveHint=true (e.g. resumed services incur billing) or whether resuming already-running services is a no-op despite idempotentHint.

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 trigger condition, then the exception, then the return value. No filler, though the 'with why' phrasing at the end is slightly informal.

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?

With no output schema, the description usefully tells the agent the result reports resumed vs skipped items and reasons, and warns about the billing-blocked case. Missing only sibling differentiation and the rationale for the destructive annotation.

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 documents it fully (name, slug, or ID at 100% coverage). The description mentions 'a Lizard project' but adds no syntax or format guidance beyond the schema, so 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?

Specific verb+resource: 'start again the services of a Lizard project' clearly scopes a project-level bulk resume. It implicitly contrasts with service_resume/workspace_resume by operating on all services of a project, but never names those siblings, so an agent must infer the granularity distinction.

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 start again the services of a Lizard project that they paused' gives a clear triggering condition, and the billing-freeze sentence states a case where the tool will not fully succeed. No explicit alternative routing (e.g. to service_resume for a single service) is provided.

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