Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-stop

Idempotent

Stops a running LibSQL database instance by ID so you can halt it when no longer needed or pause it during maintenance.

Instructions

POST /libsql.stop

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": {
      "libsqlId": "<libsqlId>"
    },
    "name": "libsql-stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations supply idempotentHint=true and openWorldHint=true, so the safety profile is partly covered by structured data, but the description adds zero context beyond the route. It does not say whether stopping is graceful, whether data/volumes persist, whether the instance can be restarted with libsql-start, or what happens if it is already stopped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from under-specification rather than efficiency: a lone HTTP route adds no information beyond the name. There is no front-loaded statement of action or effect for the agent to anchor on.

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

Completeness2/5

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

For an operation that mutates instance lifecycle state, with one undocumented required parameter and no output schema, the description should explain the effect and follow-up path. Nothing beyond annotations is provided, so an agent has insufficient information to call this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter libsqlId, so the schema only provides a type and minLength. The description does not explain what identifier is expected, where to obtain it, or whether it is the instance name or a system ID, leaving the one required parameter semantically unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only the raw route string "POST /libsql.stop", which restates the tool name and HTTP verb rather than stating in prose what the tool does. An agent can guess it stops a libSQL instance, but nothing distinguishes it from siblings like libsql-start, libsql-reload, or libsql-remove beyond the name itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as libsql-start or libsql-reload. The agent must infer the entire selection context from the tool name.

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