Greeter MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| 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 ambiguity or overlap between tools. The single tool 'greet' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming is trivially consistent because there is only one tool. The tool name 'greet' follows a simple verb pattern, and with no other tools to compare against, there are no inconsistencies in naming conventions.
A single tool is generally too few for most server purposes, as it limits functionality and can feel thin. For a 'Greeter' server, while a single greeting tool might suffice for basic use, it lacks depth and may not support varied interactions or extended features that agents might expect.
The server is severely incomplete for a greeter domain. With only a 'greet' tool, there are obvious gaps such as no ability to customize greetings, handle different languages, manage user preferences, or provide follow-up interactions. This minimal surface will likely cause agent failures in more complex scenarios.