Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Restore Db

restore_db

Restore the Metis database from a .sqlite backup while preserving the current live database as a timestamped pre-restore copy; restart the dashboard afterward.

Instructions

Restore the Metis database from a backup.

Renames the current live database to <db>.pre-restore.<timestamp>
before overwriting, so you can recover if something goes wrong.

IMPORTANT: This overwrites the live database. All changes since the backup
was taken will be lost. The dashboard must be restarted after restore.

Args:
    backup_path: Full path to the .sqlite backup to restore from.
    confirm:     Must be the string 'YES' to proceed.

Returns JSON with status and paths.

Input Schema

NameRequiredDescriptionDefault
confirmNo
backup_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it renames the current database, overwrites the live database, loses all changes since backup, and requires a restart after restore.

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?

The description is well-structured with sections for purpose, important warnings, and args. It is slightly verbose but front-loads critical information efficiently.

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?

Given the destructive nature and existence of an output schema, the description adequately covers prerequisites, behavioral details, and post-action requirements, making it complete for an agent to use safely.

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

Parameters5/5

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

Schema coverage is 0%, but the description adds crucial meaning: backup_path is described as a full path to .sqlite backup, and confirm must be the string 'YES' to proceed, which is not clear from the schema alone.

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 clearly states 'Restore the Metis database from a backup' with a specific verb and resource. It distinguishes itself from the sibling 'backup_db' by being the restore counterpart.

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

Usage Guidelines3/5

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

The description implies usage for restoring from a backup and warns about overwriting and restart, but does not explicitly guide when to use this tool versus alternatives like backup_db or list_backups.

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