Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Serverless status

service_sleep_status
Read-onlyIdempotent

Check whether a Lizard app or database is serverless and sleeps when idle; returns enabled status, idle minutes, sleep/wake counts, and last sleep error.

Instructions

Use this when the user asks whether a Lizard service (app or Postgres/Redis database) is serverless, i.e. sleeps when idle: returns enabled, idleMinutes, how many times it slept and woke, and the last error if it could not sleep.

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

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

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds genuine value by listing exactly what the response contains, including the last error if the service could not sleep. It does not discuss permissions or behavior when the service is not serverless-enabled, which keeps it below a 5.

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?

One sentence, front-loaded with the usage trigger, and the return payload is spelled out without filler. It is dense but every clause carries information; slight density is the only knock.

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?

With full schema coverage and rich annotations but no output schema, the description does exactly the remaining work: it tells the agent what the call returns. Nothing needed to select or invoke 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 coverage is 100%, so both parameters are already documented, and the description's parenthetical about app-vs-database services largely restates the schema's 'App or database name or ID'. Baseline 3 is appropriate.

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?

The description states a specific action and resource: it reports whether a Lizard service (app or Postgres/Redis database) is serverless/sleeps when idle, and enumerates the returned fields (enabled, idleMinutes, sleep/wake counts, last error). That field list clearly separates it from service_show and service_sleep_set.

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?

It gives an explicit trigger: 'Use this when the user asks whether a Lizard service ... is serverless, i.e. sleeps when idle.' There is no explicit exclusion naming the sibling to use for changing the setting (service_sleep_set), but the read-only framing makes the boundary reasonably clear.

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