wsqlite-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_model_schemaA | Validate a Pydantic model definition for WSQLite compatibility. Checks for common issues:
|
| generate_migration_from_modelsC | Generate a migration file from Pydantic model definitions. Parses model definitions and creates a migration that creates tables matching the model schemas. Returns the migration code as a string. |
| search_wsqlite_patternB | Search for production-ready SQLite patterns in official catalog. |
| deploy_wsqlite_scaffoldingC | Deploys a professional WSQLite project structure following wisrovi standards. |
| get_wsqlite_architect_blueprintsA | Complete reference with read/write/update examples for every WSQLite feature. |
| get_wsqlite_architect_manualB | Expert manual for building high-performance SQLite-backed systems (wisrovi standard). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes: validation, migration generation, pattern search, scaffolding deployment, and reference. However, 'get_wsqlite_architect_blueprints' and 'get_wsqlite_architect_manual' have overlapping descriptions as reference materials, causing slight ambiguity.
Tool names follow a consistent verb_noun pattern in snake_case (validate, generate, search, deploy, get). The 'generate_migration_from_models' is slightly longer than others, and the two 'get_wsqlite_architect_*' tools share a prefix, but overall the naming is predictable and readable.
Six tools is well-scoped for a development-oriented server, covering validation, migration, search, scaffolding, and documentation. Each tool fills a clear role without redundancy.
The toolset covers the core workflow of model validation and migration generation, plus project scaffolding and reference lookup. Missing tools for applying migrations or direct model CRUD, but these gaps are not critical for a development assistant.