Skip to main content
Glama
Sign In
SQLite MCP Server

SQLite MCP Server

by stevefordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_databases

Search across multiple SQLite databases in a directory to find tables and columns containing a specific keyword.

Instructions

Search for a keyword in all SQLite databases within a directory. Searches table names and column names to help discover relevant data.

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": {
      "path": "<path>",
      "query": "<query>"
    },
    "name": "search_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

B3.2/5.0
Behavior3/5

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

Discloses it searches table and column names, but no annotations exist. Does not mention scope boundaries, error conditions, or performance considerations.

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 with no redundancy. Action and scope are front-loaded, second sentence adds relevant detail concisely.

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?

Simple tool with two parameters and an output schema. Description is adequately complete for its complexity, though could mention that it targets SQLite databases only.

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 0%; description only implies 'path' is a directory and 'query' is a keyword, but does not explicitly define them or provide format details.

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?

Description clearly states it searches a keyword across all SQLite databases in a directory, specifically table and column names. It distinguishes from siblings like list_databases or describe_table, though not explicitly stating the difference.

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 versus alternatives (e.g., list_tables, execute_query). Lacks when-not conditions 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

Other Tools