fastmcp-sqlite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| schemaA | Get the schema of a SQLite database: all tables, views, columns, data types, constraints, indexes, foreign keys, and sub-millisecond O(1) row counts. |
| queryA | Execute a SQL query against a SQLite database with parameter binding and token-efficient formatting. Returns results as Markdown table, vertical record view, or JSON. Protected by opcode execution watchdog and cell truncation. |
| export_queryA | Execute a SQL query and stream results directly to a local CSV or JSONL file on disk. Zero token consumption, constant O(1) memory usage, ideal for large query exports. |
| table_infoA | Get detailed info about a single table or view: columns, types, constraints, indexes, foreign keys, triggers, DDL SQL, and row count estimation. |
| explainA | Explain the query plan for a SQL query (EXPLAIN QUERY PLAN). Helps analyze indexes and optimize query performance. |
| list_databasesA | List all SQLite database files (.db, .sqlite, .sqlite3) in a directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct scope: whole-database schema vs. single-table details, in-chat query results vs. file export, query plan analysis, and database file discovery. There is no meaningful overlap or ambiguity between them.
Names are readable and consistently lowercase snake_case, but they mix noun-style resource names (schema, table_info) with verb-style action names (query, export_query, explain, list_databases). A consistent verb_noun or get_/list_ pattern would improve predictability.
Six tools is a well-scoped set for a SQLite database server. Each tool serves a distinct need—exploration, querying, export, and query planning—without unnecessary duplication or bloat.
Within the apparent read/analysis-oriented scope, the tool surface is complete: it covers database discovery, schema inspection, detailed table metadata, querying, query plan explanation, and large result exports. There are no obvious dead ends or missing operations for this stated purpose.