MCP Server Starter
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_named_queryC | Execute a parameterized, allow-listed SQL template |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as executing parameterized SQL queries, making it distinct by default.
The single tool name follows a clear verb_noun pattern (run_named_query), and with no other tools to compare, consistency is inherently perfect. There are no deviations or mixed conventions to assess.
One tool is too few for a server named 'MCP Server Starter', which suggests a broader or more foundational purpose. This minimal set feels thin and under-scoped, limiting functionality and likely causing gaps in coverage for typical server operations.
The tool surface is severely incomplete for a server starter kit. It only provides query execution, lacking essential operations like setup, configuration, listing available queries, or managing templates, which are critical for a comprehensive starter experience.