MCP Greeting 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetA | Returns an appropriate greeting based on the current time (good morning, good afternoon, or good evening) |
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
Only one tool exists, so there is no possibility of confusion or overlap. The single 'greet' tool is unambiguous in its purpose.
The tool name 'greet' is a clear, concise verb that directly matches the server's purpose. With only one tool, naming consistency is inherently maintained.
The server's scope is limited to providing time-based greetings, and a single tool fully fulfills that purpose. The count is appropriate for the narrow, well-defined domain.
The tool covers the full range of greeting categories (morning, afternoon, evening) and requires no additional operations. The surface is completely sufficient for its stated purpose.