mcp-server-template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TEMPLATE_AUTH_KEYS | No | Authentication keys for the server. Injected from secret manager for deployment. |
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 |
|---|---|
| run_queryA | Run a read-only SQL query with bound parameters |
| describe_tablesA | List queryable tables and their columns |
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 2 tools
run_query executes SQL statements while describe_tables returns schema metadata. The two tools have no functional overlap and are easy to distinguish.
Both tools follow the same lowercase verb_noun pattern: run_query and describe_tables. Naming is predictable and consistent.
Two tools is on the low end of reasonable for a focused read-only database server. The set is coherent but feels thin, leaving little flexibility for more advanced exploration.
The pair covers the core need of read-only SQL querying with schema discovery support. Minor gaps exist, such as no ability to inspect detailed table statistics or relationships, but agents can generally accomplish their main tasks.