Skip to main content
Glama
Sign In
SQLite MCP Server

SQLite MCP Server

by stevefordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_databases

Lists all SQLite database files (.db, .sqlite, .sqlite3) in the specified directory, defaulting to the current folder, enabling easy location of databases for analysis.

Instructions

List all SQLite database files (.db, .sqlite, .sqlite3) in the specified directory. Default is the current directory.

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_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation (listing files) but does not explicitly state that it is non-destructive, nor does it describe behavior like recursion depth or error handling.

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?

Two sentences front-load the purpose and parameter, with no redundant or extraneous information.

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

Completeness4/5

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

Given the presence of an output schema and the simplicity of the tool, the description covers the primary purpose and parameter. It could optionally mention search depth (top-level only or recursive), but it is generally sufficient.

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 schema has 0% description coverage on the 'path' parameter, but the description adds meaning by identifying it as a directory and noting the default. However, it lacks details on format, relative vs. absolute paths, or validation.

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 clearly states it lists SQLite database files (.db, .sqlite, .sqlite3) in a specified directory. This specific verb+resource combination distinguishes it from sibling tools like list_tables and search_databases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for discovering database files in a directory, but it does not provide explicit guidance on when to use this tool versus alternatives or mention any prerequisites or caveats.

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

Deploy Server

Other Tools