Skip to main content
Glama
RestDB

Codehooks.io MCP Server

by RestDB

drop_collection

Delete a collection from your database by specifying its name.

Instructions

Delete a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesName of collection to drop

Implementation Reference

  • Zod schema defining input for drop_collection: requires 'collection' (string) - the name of the collection to drop.
    const dropCollectionSchema = z.object({
        collection: z.string().describe("Name of collection to drop"),
    });
  • src/index.ts:340-351 (registration)
    Tool definition registration in the tools array: name 'drop_collection', description 'Delete a collection', with inputSchema requiring 'collection'.
    {
        name: "drop_collection",
        description: "Delete a collection",
        schema: dropCollectionSchema,
        inputSchema: {
            type: "object",
            properties: {
                collection: { type: "string", description: "Name of collection to drop" }
            },
            required: ["collection"]
        }
    },
  • Handler for drop_collection tool execution. Extracts 'collection' from args, builds CLI command 'dropcollection' with project/space/collection params, and executes via coho CLI.
    case "drop_collection": {
        const { collection } = args as DropCollectionArgs;
        const dropCollArgs = [
            'dropcollection',
            '--project', config.projectId,
            '--space', config.space,
            collection
        ];
        const result = await executeCohoCommand(dropCollArgs);
        return {
            content: [
                {
                    type: "text",
                    text: result
                }
            ],
            isError: false
        };
    }
Behavior2/5

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

No annotations provided. The description does not state that deletion is irreversible or that it removes all documents in the collection. For a destructive operation, more transparency is needed.

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 a single sentence with no wasted words. It is front-loaded and efficient, though could benefit from slight expansion.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is minimally adequate. However, missing behavioral details (e.g., irreversibility) and usage context make it less complete.

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 coverage is 100% (single parameter with description). The description adds no extra meaning beyond what the schema already provides, so baseline score of 3.

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 'Delete a collection' clearly states the verb (delete) and resource (collection), distinguishing it from sibling tools like create_collection, cap_collection, etc.

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 on when to use this tool versus alternatives like cap_collection or drop_index. No prerequisites (e.g., collection must exist) or consequences mentioned.

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/RestDB/codehooks-mcp-server'

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