Skip to main content
Glama
andyfe76

CouchDB MCP Server

by andyfe76

couchdb_list_databases

Retrieve a list of all databases available in your CouchDB server for database management and administration tasks.

Instructions

List all databases in the CouchDB server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function _list_databases() that executes the tool logic - retrieves all databases from the CouchDB server, formats the result with count, and returns as JSON
    async def _list_databases(self) -> list[TextContent]:
        """List all databases."""
        databases = list(self._get_server())
        result = {
            "databases": databases,
            "count": len(databases)
        }
        return [TextContent(type="text", text=json.dumps(result, indent=2))]
  • Registration in call_tool() - maps the tool name 'couchdb_list_databases' to its handler method _list_databases()
    if name == "couchdb_list_databases":
        return await self._list_databases()
  • Tool schema definition - declares the tool name, description, and input schema (empty object, no parameters required)
    Tool(
        name="couchdb_list_databases",
        description="List all databases in the CouchDB server",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Helper method _get_server() that returns the CouchDB server connection, connecting if needed
    def _get_server(self) -> couchdb.Server:
        """Return the CouchDB server, connecting if needed."""
        if self.couch is None:
            self.connect()
        assert self.couch is not None
        return self.couch
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't specify details like whether it returns all databases at once (vs. paginated), requires authentication, has rate limits, or what format the output takes. This is inadequate for a tool with zero annotation coverage.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse. Every part of the sentence contributes directly to understanding the tool's purpose.

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 tool's simplicity (0 parameters, no output schema), the description is minimal but incomplete. It lacks behavioral context (e.g., output format, authentication needs) and usage guidelines, which are important even for simple tools. Without annotations or output schema, the description should provide more completeness for the agent to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description doesn't need to add parameter details, and it correctly implies no inputs are required. A baseline of 4 is appropriate as it doesn't mislead about parameters.

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 ('List all') and resource ('databases in the CouchDB server'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'couchdb_list_documents' or 'couchdb_list_indexes', which would require mentioning it's specifically about databases rather than documents or indexes.

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., server connectivity), context for usage (e.g., before creating/deleting databases), or comparisons to siblings like 'couchdb_search_documents' for filtered queries. This leaves the agent with minimal direction.

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