Skip to main content
Glama

docker_db_admin

Destructive

Back up a database container by writing a dump inside it, or restore a database from a dump already there, requiring confirmation before overwriting.

Instructions

backup takes a dump of a database container, restore fills the database from one. The answer names the file, its size and whether it was read back: a call that says done without naming a file of known size says nothing. Restore overwrites what is there and is refused without confirm — take a backup here first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoPath of the dump inside the container. Required by action restore. For backup the default is a name with the time of day under /backups, which must be a directory the container already has.
cleanNoDrop what is already there before writing, for action restore. Archive backups only (.dump, .backup) for PostgreSQL. Default: false.
actionYesbackup writes a dump inside the container and reads it back to say how large it is. restore fills the database from a dump that is already there, overwriting what it holds.
formatNoShape of the dump, for action backup. Default: the one this engine dumps in — an archive for PostgreSQL, plain SQL for MySQL, its own archive for MongoDB. A format the client has no flag for is refused.
tablesNoOnly these tables, for action backup. Default: the whole database. MongoDB takes one collection at a time.
confirmNoWritten out as "# CONFIRMED-DESTRUCTIVE", this allows one restore to overwrite the database. Anything else leaves the refusal standing.
profileNoWhich Docker host, by profile name. Default: the profile marked as default.
projectNoWhich compose project. Default: the project of the working directory. A name matching nothing is an error, not a fall back to every container on the host.
serviceYesService name as written in the compose file.
compressNoCompress the dump, for action backup. Only where the client compresses by itself. Default: true.
dataOnlyNoWrite the rows and leave the schema alone, for action restore. Default: false.
databaseNoWhich database to fill, for action restore. Default: the one the container was started with.
schemaOnlyNoWrite the schema and none of the rows, for action restore. Default: false.
compose_pathNoWhere the compose file is: the file itself, or the directory holding it. Needed only when no container of the host carries the project label — a project that was never brought up there. A directory holding several compose files is refused with their names rather than guessed through.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNo
bytesNo
actionNo
engineNo
legendNoWhat the words in this answer mean. A key names the field before the value — "state=running", "containers[].health=unhealthy" — and only the values this answer used are listed.
reasonNo
messageNo
projectNo
serviceNo
verifiedNo
confirmedNo
restartedNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description reveals important behavioral traits: restore overwrites data, is refused without confirm, backup verifies by reading back, and the result must name a file of known size. This materially helps an agent understand what to expect and demand from the tool.

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

Conciseness5/5

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

Two dense sentences with no filler. The actions are front-loaded, and every clause adds either behavioral guidance or a verification requirement that an agent would otherwise miss.

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?

For a complex 14-parameter tool, the description covers the critical safety and verification behaviors while relying on the richly documented schema for parameter details. It is missing only an explicit distinction from docker_db, but otherwise gives sufficient context.

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 description coverage is 100%, so the structured schema already documents all parameters. The description adds useful context around confirmation and output verification, but does not add parameter-specific semantics beyond what the schema provides.

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?

The description names specific actions ('backup takes a dump of a database container, restore fills the database from one') and the resource being operated on. It clearly distinguishes the two modes, though it does not explicitly differentiate this tool from the sibling docker_db.

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?

The description gives clear operational context: restore is destructive, requires confirmation, and should be preceded by a backup ('take a backup here first'). It does not explicitly state when to choose this tool over docker_db, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hypnosis/docker-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server