Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-saveExternalPorts

Idempotent

Configures external HTTP, gRPC, and admin ports for a LibSQL instance using its ID, so clients can connect through the intended exposed ports.

Instructions

POST /libsql.saveExternalPorts

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

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes
externalPortNo
externalGRPCPortNo
externalAdminPortNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the safety/repeatability profile is partly covered by structured data. The description adds nothing beyond that: it does not say what happens when a port field is null (clear vs. leave unchanged), whether a redeploy/restart is triggered, what permissions are needed, or what the response contains. No contradiction with annotations, but no added behavioral value either.

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?

The single route string is technically short with no filler, but this is under-specification rather than conciseness. There is no front-loaded statement of purpose, so the brevity costs the agent all actionable information.

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?

For a four-parameter mutation tool with no output schema and only partial annotations, the description should carry the burden of explaining target identification, null-port semantics, and side effects. It covers none of these, leaving the agent unable to invoke the tool correctly without guessing.

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?

Schema description coverage is 0% across four parameters, and the description supplies no parameter meaning at all. It never explains that libsqlId identifies the target instance or, critically, whether the three nullable port fields (externalPort, externalGRPCPort, externalAdminPort) are cleared, preserved, or auto-assigned when null.

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 HTTP route "POST /libsql.saveExternalPorts", which essentially restates the tool name in REST terms. It conveys that this is a write (POST) to persist external ports for a libsql instance, but gives no domain-level statement of what the operation actually accomplishes or how it differs from the parallel mariadb/mysql/postgres saveExternalPort siblings.

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 settings-getTraefikPorts/updateTraefikPorts or the sibling saveExternalPort tools for other engines. At best the name plus POST implies 'use this to persist external port assignments for a libsql instance', which an agent must infer rather than read.

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