Skip to main content
Glama
QueryPilot MCP

QueryPilot MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QUERYPILOT_TIMEOUTNoQuery timeout in seconds. Can be lowered, not raised.30
QUERYPILOT_DATA_DIRYesRequired. The only folder the agent can see.
QUERYPILOT_LOG_FILENoPath to the audit log file. Must be outside the data folder.~/.querypilot/queries.jsonl
QUERYPILOT_MAX_ROWSNoMaximum number of rows returned. Can be lowered, not raised.1000
QUERYPILOT_SEMANTICNoPath to an optional semantic.yaml glossary.<data-dir>/semantic.yaml if it exists

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

QueryPilot gives you READ-ONLY SQL access (DuckDB dialect) to local data files. Suggested workflow:

  1. list_tables to see what exists.

  2. describe_table for columns, types and statistics.

  3. get_definitions to learn business terms (e.g. what "revenue" means here).

  4. sample_rows to look at real values.

  5. run_query with ONE SELECT statement. Results are capped (default 1000 rows) and queries stop after 30 seconds. Write, DDL, file and settings access is blocked.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tablesA

List every table you can query, with the file it came from.

describe_tableB

Show the columns of a table with types and statistics (row count, min, max, average, distinct values, % nulls).

sample_rowsB

Return the first n rows of a table (1-50, default 5).

run_queryA

Run ONE read-only SELECT (DuckDB SQL) on the tables from list_tables. Returns at most max_rows rows (hard cap 1000); 'truncated' is true if more rows existed. Queries are stopped after 30 seconds.

get_definitionsA

Business glossary from semantic.yaml: what terms like 'revenue' mean and what each column contains. Leave 'term' empty to get all.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct stage of the data exploration workflow: discovering tables, inspecting schema/stats, sampling rows, retrieving glossary definitions, and executing SQL. The only mild overlap is between describe_table and get_definitions, but one gives schema/statistics while the other gives business semantics, so an agent can easily choose correctly.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern (list_tables, describe_table, sample_rows, get_definitions, run_query). The wording is predictable and readable, with no mixed casing or inconsistent verb styles.

Tool Count5/5

Five tools is well-scoped for a read-only DuckDB query assistant. Every tool adds a necessary capability, and there is no redundant or filler tool.

Completeness4/5

The surface covers the core read-only lifecycle: discover tables, inspect schemas, sample data, understand business terms, and run constrained SELECT queries. Minor gaps exist around searching for columns by name, inspecting relationships/foreign keys, or explaining query plans, but agents can work around these using describe_table and run_query.