Skip to main content
Glama
Sign In
Windows Developer MCP Server

Windows Developer MCP Server

by peeyushcodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqlite_query

Retrieve data from a SQLite database using read-only SELECT statements. Supports parameterised queries and configurable row limits.

Instructions

Execute a read-only SELECT query against a SQLite database.

Only SELECT statements are allowed. Use sqlite_execute for writes.

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": {
      "database": "<database>",
      "sql": "<sql>"
    },
    "name": "sqlite_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesThe SELECT query to execute.
paramsNoOptional query parameters (for parameterised queries).
databaseYesPath to the database file.
max_rowsNoMaximum rows to return (1–5000). Default: 500.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description takes on the burden of disclosing behavior. It clearly states 'read-only' and 'Only SELECT statements are allowed', which are key behavioral traits. It doesn't mention return format or edge cases, but the output schema handles that. A 4 is appropriate.

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 filler. The action is front-loaded and the alternative tool is mentioned without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a clear scope, all params are documented, and an output schema exists. The description covers the core safety and usage context, making it sufficient for an agent to invoke correctly.

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

Parameters3/5

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

The input schema provides 100% description coverage for all 4 parameters, so the baseline is 3. The description reinforces that the sql parameter must be a SELECT query, but doesn't add meaningful details beyond the 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 states 'Execute a read-only SELECT query against a SQLite database', which is a specific verb+resource+scope. It distinguishes from sqlite_execute by explicitly noting 'Use sqlite_execute for writes'.

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

Usage Guidelines5/5

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

It explicitly says 'Only SELECT statements are allowed' and directs users to sqlite_execute for writes, providing a clear alternative. This makes it obvious when to use this tool versus siblings.

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