mcp-forge
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | Lists all user tables in the SQLite database. |
| describe_tableA | Describes the schema and column definitions of a specific table. |
| execute_queryB | Executes a SQL SELECT query on the SQLite database and returns rows. |
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 3 tools
Each tool targets a clearly distinct layer: enumerating tables, inspecting one table's schema, and running row-returning queries. An agent can trivially pick the right one from names alone. No overlap between describe_table (metadata) and execute_query (data).
All three follow the verb_noun snake_case pattern (list_tables, describe_table, execute_query), which is highly predictable. The only minor inconsistency is singular vs. plural nouns (tables vs. table), though that actually reflects list-vs-single semantics.
Three tools is on the thin edge for a database server; a listing, a schema descriptor, and one query executor cover the basics but leave little room for inspection workflows. It's borderline rather than wrong-sized, since the surface is deliberately minimal.
Read-only exploration is covered, but execute_query is explicitly limited to SELECT, so there is no way to create tables, insert, update, or delete — an obvious gap for a database tool. Agents hitting a need to mutate data or run DDL will dead-end, though exploration tasks are fully served.