Skip to main content
Glama
Sign In
pocketbase-mcp

pocketbase-mcp

by nestebe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete backup

delete_backup

Delete a specified backup file by its key. Permanently removes the backup and requires superuser access.

Instructions

Delete a single backup file by its key/name. Cannot be undone. Superuser only.

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": {
      "key": "<key>"
    },
    "name": "delete_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesBackup file key/name (as returned by list_backups).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses irreversibility ('Cannot be undone') and an access restriction ('Superuser only'), which are critical behavioral traits for a destructive operation. This goes beyond simple 'deletes' and prepares the agent for the consequence.

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?

The description consists of three short distinct sentences: action, warning, and permission. Every sentence carries unique, necessary information with no redundancy or filler.

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 one-parameter destructive tool with full schema coverage and no output schema, the description covers the action, parameter identification, irreversibility, and access control. It could mention error behavior or whether the backup is permanently removed from storage, but nothing essential for correct invocation is missing.

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?

The input schema already provides 100% coverage for the single 'key' parameter, including the source ('as returned by list_backups'). The description's phrase 'by its key/name' adds no new semantic information beyond the schema, so the baseline of 3 applies.

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 states a specific verb ('Delete'), a clear resource ('backup file'), and a precise scope ('single... by its key/name'). This distinguishes it from sibling backup tools like list_backups, restore_backup, and get_backup_download_url, and from deletion tools for other resources.

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?

Usage is implied rather than explicit: the verb and resource make it clear this tool removes backups, but the description does not name alternatives or state when not to use it. 'Superuser only' provides an access condition but no comparative routing guidance.

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