cloudflare-mcp-pro

list_d1_databases

Read-only

List all D1 databases in your Cloudflare account, with optional name filter and pagination support.

Instructions

List D1 databases in an account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_d1_databases"
  }
}

Input Schema

Name	Required	Description
`account_id`	No	Cloudflare account ID. Falls back to CLOUDFLARE_ACCOUNT_ID env var when omitted.
`name`	No	Filter by database name.
`page`	No
`per_page`	No
`fetch_all`	No	When true, follow pagination and return all pages combined (ignores page/per_page).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=true, so the safety profile is clear. However, the description adds no information about pagination behavior, rate limits, or the effect of the 'fetch_all' parameter. The behavioral detail is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it omits essential details, making it under-specified. Conciseness is achieved at the expense of completeness.

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 has 5 parameters and no output schema, the description should cover pagination, filtering, and the use of 'fetch_all'. It only mentions the basic action, leaving many important aspects undocumented.

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

Parameters2/5

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

Schema coverage is 60% with two parameters (page, per_page) lacking descriptions. The description does not explain these parameters or their interaction (e.g., pagination logic, default values). It adds no semantic value beyond the 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 ('list') and resource ('D1 databases') and distinguishes from sibling list tools for other resources. However, it lacks specifics on scope (e.g., account-wide) and does not fully differentiate from other list 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 on when to use this tool vs alternatives like query_d1 or create_d1_database. No prerequisites or usage contexts are provided, leaving the agent to infer from context.

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

Deploy Server