Skip to main content
Glama
robertoamoreno

CouchDB MCP Server

deleteDatabase

Remove a CouchDB database by specifying its name to free up storage space or clean up unused data.

Instructions

Delete a CouchDB database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbNameYesDatabase name to delete

Implementation Reference

  • Core handler function that performs the database deletion using CouchDB Nano client's destroy method.
    export async function deleteDatabase(dbName: string): Promise<void> {
      await couch.db.destroy(dbName);
    }
  • Input schema for the deleteDatabase tool, defining the required dbName parameter.
    {
      name: 'deleteDatabase',
      description: 'Delete a CouchDB database',
      inputSchema: {
        type: 'object',
        properties: {
          dbName: {
            type: 'string',
            description: 'Database name to delete',
          },
        },
        required: ['dbName'],
      },
    },
  • src/index.ts:234-235 (registration)
    Registration of the tool in the CallToolRequestSchema switch dispatcher.
    case 'deleteDatabase':
      return this.handleDeleteDatabase(request.params.arguments);
  • Wrapper handler method that validates input, calls the core deleteDatabase function, and formats the MCP response.
    private async handleDeleteDatabase(args: any) {
      if (!args.dbName || typeof args.dbName !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid database name');
      }
    
      try {
        await deleteDatabase(args.dbName);
        return {
          content: [
            {
              type: 'text',
              text: `Database ${args.dbName} deleted successfully`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Error deleting database: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete' which implies a destructive mutation, but doesn't disclose critical behavioral traits: whether deletion is permanent, if it requires specific permissions, what happens to contained documents, or error conditions. This is a significant gap for a destructive 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?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion (success/failure responses), doesn't warn about irreversible data loss, and doesn't provide context about the CouchDB environment. For a tool that permanently removes resources, this lacks critical completeness.

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% (the single parameter 'dbName' is fully described in the schema as 'Database name to delete'). The description doesn't add any parameter meaning beyond what the schema provides, so it meets the baseline of 3 when schema does the heavy lifting.

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 clearly states the action ('Delete') and target resource ('a CouchDB database'), providing specific verb+resource pairing. It doesn't explicitly distinguish from sibling tools like 'createDatabase' or 'listDatabases', but the verb 'Delete' inherently differentiates it from creation and listing operations.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., database must exist), consequences (e.g., irreversible data loss), or relationships to sibling tools like 'createDatabase' for recreation or 'listDatabases' for verification.

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

Install Server

Other Tools

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/robertoamoreno/couchdb-mcp-server'

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