pocketbase-mcp

Delete superuser

delete_superuser

Remove a superuser account by ID while ensuring at least one admin remains in PocketBase.

Instructions

Delete a superuser (admin) account by id. At least one superuser must always remain.

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": {
      "id": "<id>"
    },
    "name": "delete_superuser"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Superuser record id to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It plainly states the destructive action and adds a meaningful safety constraint, but it does not mention irreversibility, permission requirements, or what happens if the last superuser is targeted.

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 is two short, front-loaded clauses with no wasted words. It communicates the action, target, identification method, and an important constraint efficiently.

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 single-parameter delete operation with no output schema, the description is largely complete: it names the action, the target, how to identify it, and a key business rule. It could optionally note irreversibility or failure behavior, but the essential information is present.

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 schema already fully documents the single required 'id' parameter with 100% coverage. The description's phrase 'by id' aligns with the schema but adds no substantive new meaning beyond what is already present.

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 and resource: 'Delete a superuser (admin) account by id.' It clearly distinguishes itself from the sibling superuser tools, which create, update, or list superusers rather than deleting them.

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 its use for removing a superuser account and provides an important guardrail: 'At least one superuser must always remain.' However, it does not explicitly state when to prefer this tool over alternatives like update_superuser, nor does it describe any prerequisites or exclusions.

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

Deploy Server