Skip to main content
Glama
seek-your-way-out

Cloudflare D1 Database MCP Server

d1_list_tables

Retrieve a list of all tables in your Cloudflare D1 database to understand database structure and plan SQL operations.

Instructions

List tables available in the Cloudflare D1 database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'd1_list_tables' tool in the CallToolRequestSchema. It calls client.listTables() and formats the result as JSON text response.
    } else if (name === "d1_list_tables") {
      const tables = await client.listTables();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(tables, null, 2)
          }
        ]
      };
  • src/server.ts:50-58 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and empty input schema.
    {
      name: "d1_list_tables",
      description: "List tables available in the Cloudflare D1 database.",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false
      }
    }
  • Implementation of listTables() method in D1Client, which queries sqlite_master for table names using a SQL statement and processes the result.
    async listTables(): Promise<string[]> {
      const sql = `SELECT name FROM sqlite_master WHERE type = 'table' ORDER BY name;`;
      const result = await this.executeQuery(sql);
    
      if (!result.success) {
        const error = result.errors?.[0]?.message ?? "Unknown D1 error";
        throw new Error(`Failed to list tables: ${error}`);
      }
    
      const rows = Array.isArray(result.result) ? result.result : [];
      const firstResult = Array.isArray(rows[0]) ? rows[0] : rows;
    
      if (!Array.isArray(firstResult)) {
        return [];
      }
    
      // D1 returns rows as array of objects { name: string }
      return firstResult
        .filter((item): item is { name: string } => typeof item === "object" && item !== null && "name" in item)
        .map((row) => row.name);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but does not describe traits like whether it's read-only, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 that directly states the tool's purpose without any fluff or redundant information. It is front-loaded and appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It covers the basic action but does not provide context on behavioral traits or output, which could be important for an agent to use it effectively in a broader workflow.

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, and the input schema has 100% description coverage (though empty). The description does not need to add parameter details, so it appropriately avoids redundancy. A baseline score of 4 is given as it efficiently handles the lack of parameters without unnecessary information.

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 ('List') and resource ('tables available in the Cloudflare D1 database'), making the purpose immediately understandable. However, it does not explicitly differentiate from its sibling tool 'd1_query', which might also involve table operations, so it falls short of a perfect score.

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, such as the sibling 'd1_query'. It lacks any mention of prerequisites, context, or exclusions, leaving the agent to infer usage based solely on the tool name and description.

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/seek-your-way-out/cloudflare-sywo-mcp-server'

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