Skip to main content
Glama
Sign In
mcp-server-sqlite

mcp-server-sqlite

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

schema

Retrieve the complete schema of a SQLite database, including all tables, columns, and row counts for database analysis and inspection.

Instructions

Get the schema of a SQLite database: all tables with columns and row counts.

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

Input Schema

NameRequiredDescriptionDefault
dbYesPath to the .db or .sqlite file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the tool's behavior as a read operation that returns schema information, but doesn't mention error handling, performance characteristics, or output format details. It adequately describes what the tool does without contradictions.

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?

The description is a single, efficient sentence that immediately states the tool's purpose and scope. Every word earns its place with no redundancy or unnecessary elaboration, making it easy to parse and understand quickly.

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

Completeness3/5

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

For a single-parameter read tool with no annotations and no output schema, the description provides adequate context about what the tool does. However, it doesn't describe the return format or structure, which would be helpful given the lack of output schema. The description is complete enough for basic understanding but could be more comprehensive.

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 description coverage is 100%, so the input schema already documents the single parameter 'db' as a path to a database file. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score for high schema coverage.

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 clearly states the specific action ('Get the schema') and resource ('SQLite database'), with precise scope ('all tables with columns and row counts'). It distinguishes from sibling tools like 'query' (executes queries) and 'table_info' (likely provides detailed table metadata) by focusing on comprehensive schema retrieval.

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 description implies usage when needing database structure information, but doesn't explicitly state when to use this tool versus alternatives like 'table_info' or 'explain'. It provides basic context (SQLite databases) but lacks explicit guidance on prerequisites or exclusions.

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