Skip to main content
Glama
andyfe76

CouchDB MCP Server

by andyfe76

couchdb_create_database

Create a new database in CouchDB by specifying its name, enabling document storage and management through the MCP server.

Instructions

Create a new database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the database to create

Implementation Reference

  • The actual handler function that creates a CouchDB database. It calls self._get_server().create(name) to create the database and handles the PreconditionFailed exception when the database already exists.
    async def _create_database(self, name: str) -> list[TextContent]:
        """Create a new database."""
        try:
            self._get_server().create(name)
            return [TextContent(type="text", text=f"Database '{name}' created successfully")]
        except couchdb.http.PreconditionFailed:
            return [TextContent(type="text", text=f"Database '{name}' already exists")]
  • Tool schema definition for couchdb_create_database, including name, description, and inputSchema with required 'name' parameter for the database name.
    Tool(
        name="couchdb_create_database",
        description="Create a new database",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "Name of the database to create",
                },
            },
            "required": ["name"],
        },
    ),
  • Registration of the couchdb_create_database tool in the call_tool handler, mapping the tool name to the _create_database method with the name argument.
    elif name == "couchdb_create_database":
        return await self._create_database(arguments["name"])
Behavior2/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 states 'Create a new database' which implies a write/mutation operation, but doesn't describe what happens on success/failure, permissions required, or side effects (e.g., if it overwrites existing databases). For a mutation tool with zero annotation coverage, this is inadequate.

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 for a simple tool and front-loads the core action. Every word earns its place, making it easy for an agent to parse quickly.

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 the complexity of a database creation tool (a mutation with potential side effects), no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like error conditions, idempotency, or what is returned. The agent lacks sufficient context to use this tool safely and effectively.

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 description adds no parameter information beyond what the schema provides. However, with 100% schema description coverage (the 'name' parameter is fully documented in the schema), the baseline is 3. The description doesn't compensate with additional context like naming conventions or constraints, but doesn't need to given the comprehensive schema.

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 verb 'Create' and the resource 'new database', making the purpose immediately understandable. It distinguishes from siblings like 'couchdb_create_document' by specifying the database resource type. However, it doesn't explicitly contrast with 'couchdb_list_databases' or 'couchdb_delete_database', which would have made it a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the database must not already exist), when not to use it, or direct comparisons to siblings like 'couchdb_list_databases' for checking existing databases first. This leaves the agent without context for tool selection.

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/andyfe76/couchdb_mcp'

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