sqlite-mcp-server

Overview Schema Source Related Servers Discussions Admin

query_execution

Execute SELECT queries directly on a SQLite database to retrieve and inspect stock pricing data. Provide the database path and SQL to get results.

Instructions

Execute a SELECT query on the database.

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>",
      "sql": "<sql>"
    },
    "name": "query_execution"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	Yes
`params`	No
`db_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral facts itself. It only indicates that a SELECT is executed, suggesting read-only behavior, but does not describe return format, param binding, error behavior, or any side effects. This is a functional but incomplete behavioral picture.

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

Conciseness4/5

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

The description is a single, efficient, front-loaded sentence with no filler or repetitive content, which is well-structured for the information it conveys. It is concise, but only because it omits much necessary contextual detail.

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 existence of the 3 parameters (2 required), a missing param descriptions, and no annotations, the description is not complete enough for an agent to invoke the tool confidently. Even with an output schema present, the description fails to clarify shared parameter roles and constraints.

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

Parameters1/5

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

The input schema provides zero description coverage and the tool description says nothing about db_path, sql, or params. An agent cannot infer what values to provide or how they relate to the query execution from the description or schema.

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 reads "Execute a SELECT query on the database," which clearly identifies the verb, the resource, and the exact operation (SELECT). This also differentiates it from sibling tools list_tables and get_table_structure, which are about schema inspection, not arbitrary data queries.

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

Usage Guidelines3/5

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

The "SELECT" qualifier implies this tool is for read-only data retrieval rather than schema inspection, subtly pointing to when it should be used relative to siblings. However, the description does not state this explicitly, mention the alternatives, or provide any exclusions or prerequisites.

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

Deploy Server