mcp-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetD | – |
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 inter-tool confusion or misselection. However, the complete absence of a description leaves some uncertainty about the tool's exact purpose and usage, slightly reducing clarity.
The single tool name 'greet' is a simple verb in lowercase, which is consistent with common MCP naming conventions. There is no second tool to create a naming pattern conflict.
A single, undocumented 'greet' tool is an extreme mismatch for any meaningful server scope. The rubric explicitly treats a single trivial tool as a score of 1.
The server provides no lifecycle, CRUD, or domain-specific operations beyond a trivial greeting. This is a severely incomplete surface for any practical agent use case.