MCP Server Boilerplate
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 |
|---|---|
| make-html-pageB | Generate an HTML page using GPT-5 and save it to a file path |
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 with other tools. The tool 'make-html-page' has a clear, singular purpose that cannot be confused with any other functionality in this set.
The single tool name 'make-html-page' follows a consistent verb-noun pattern, using kebab-case. Since there is only one tool, there is no inconsistency to evaluate, and the naming convention is straightforward and appropriate.
A single tool is too few for a server named 'MCP Server Boilerplate', which implies a broader or more foundational purpose. This minimal set feels thin and underdeveloped for typical boilerplate functionality, which might include multiple utilities or examples.
The tool surface is severely incomplete for a boilerplate server. It only covers generating HTML pages, lacking any other common operations like file management, data processing, or configuration handling that would be expected in a boilerplate context, leading to significant gaps in functionality.