Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-changeStatus

Idempotent

Updates the status of a LibSQL instance by ID to idle, running, done, or error, enabling deployment state tracking and error handling.

Instructions

POST /libsql.changeStatus

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>",
      "applicationStatus": "<applicationStatus>"
    },
    "name": "libsql-changeStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes
applicationStatusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations only declare openWorldHint=true and idempotentHint=true; the description adds nothing about what the status transition means, whether it is reversible, which statuses can follow which, or what happens to a running instance. For a mutation endpoint, the description carries essentially no behavioral information.

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

Conciseness1/5

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

A single raw route string is not conciseness but under-specification; there is no front-loaded purpose statement and no structure an agent could act on beyond the name itself.

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

Completeness1/5

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

A mutating two-parameter endpoint with no output schema and no annotation coverage for write semantics needs a real description. Nothing is provided beyond the HTTP verb and path, leaving the agent unable to safely invoke it.

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

Parameters1/5

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

Both parameters are required with 0% schema description coverage, meaning neither libsqlId nor applicationStatus is documented anywhere. The description does not explain the meaning of the status enum values (idle, running, done, error) or the required identifier format, so it fails to compensate for the coverage gap.

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 string "POST /libsql.changeStatus", which restates the tool name and HTTP method. It never states the resource (a libsql instance) or what changing status actually does, so an agent cannot distinguish it from siblings like libsql-start or libsql-stop on the basis of this text.

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

Usage Guidelines1/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 any alternative. Sibling tools such as libsql-start, libsql-stop, and the other *-changeStatus tools make the absence of routing guidance especially costly here.

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