MCP Server Starter Template
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetA | Return a short greeting for a person. Use this to verify the MCP server is running. |
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 confusion between tools. The purpose is clear and singular.
There is only one tool, so there is no inconsistency. The name 'greet' follows a simple verb pattern.
Tool count is 1, which is too few for a meaningful server. Even as a starter template, it lacks the typical minimal set (e.g., a few related operations).
The server has only a single greeting tool, which does not cover any functional domain. There are obvious gaps like any actual operations or data management.