Skip to main content
Glama
Sign In
SQLite MCP Server

SQLite MCP Server

by stevefordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

execute_query

Run read-only SQL SELECT queries on a local SQLite database to retrieve and analyze data securely.

Instructions

Execute a SELECT query on the specified SQLite database. Strictly enforced as READ-ONLY: only SELECT statements are allowed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "db_path": "<db_path>",
      "query": "<query>"
    },
    "name": "execute_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
db_pathYes
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries full burden and clearly discloses the read-only constraint and SELECT-only policy. It adds behavioral context beyond basic operation, though it does not detail error handling or concurrency behavior.

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, each essential. The first states the primary action, the second adds a critical constraint. No extraneous words, information is front-loaded.

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?

For a simple tool with 2 parameters and an output schema, the description covers the core purpose and restriction. However, it omits details like database path format, query limitations, and error handling. Given minimal complexity, it is decent but could be more complete.

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 description coverage is 0%, yet the description adds no details about the parameters (db_path, query) beyond the schema. It does not specify expected formats, validation, or constraints, failing to compensate for the lack of schema descriptions.

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 the tool executes SELECT queries, specifying the action (execute), resource (SQLite database), and scope (SELECT only). It distinguishes from siblings like add_record and create_database, which modify data or create structures.

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 explicitly states that only SELECT statements are allowed and that it is read-only, providing clear guidance on when to use (for reading data) and when not (for modifications). It implicitly points to siblings like add_record for writes, though not naming them directly.

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