Skip to main content
Glama

sqlite

Read-only

Inspect tables, columns, and schema in a read-only database, then run one parameterized SELECT, WITH, or PRAGMA query to retrieve rows.

Instructions

Read-only SQLite: tables (rows, columns), schema, query (one SELECT/WITH/PRAGMA, ? params).

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

Input Schema

NameRequiredDescriptionDefault
opNo
sqlNo
pathYes
limitNo
tableNo
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description is consistent with that, adding that only a single statement is allowed and that placeholders use '?' syntax. It says nothing about what happens when a write statement is submitted, how results are shaped/sized, or how the undocumented `limit` affects output.

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?

A single front-loaded sentence with no filler; the read-only constraint and the operation list come first. The parentheticals are dense to the point of being cryptic, which costs a little clarity for the terseness gained.

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?

This is a six-parameter, multi-mode tool with zero schema descriptions and no output schema, so the description must carry a lot. It fails to explain the `table` and `limit` parameters or what each op returns, which an agent needs in order to call the tool 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?

Schema coverage is 0%, so the description carries the burden. It loosely covers four of six parameters (path implied by SQLite file, op via the three named modes, sql via the statement-type restriction, params via '? params'), but `limit` and `table` are entirely unexplained, leaving a real gap.

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?

The description names the resource (SQLite) and three concrete operations (tables, schema, query), which lets an agent distinguish this from siblings like `json` or `diff`. It is compressed to the point that 'tables (rows, columns)' is ambiguous about whether it lists tables or row/column data, but the core purpose is unambiguous.

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?

Constraints imply usage: 'Read-only' excludes writes and 'one SELECT/WITH/PRAGMA' excludes multi-statement or DDL work. Beyond that there is no guidance on which op to pick first, whether `tables` must precede `query`, or when to prefer this tool over siblings that read structured data.

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