xmcp-demo
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetC | Greet the user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review-code | Review code for best practices and potential issues |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| app-config | Application configuration data |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion. The purpose of 'greet' is completely distinct and unambiguous.
The single tool name 'greet' is a clear, concise verb that follows a simple convention. There is no inconsistency to evaluate with only one tool.
A single trivial tool like 'greet' is an extreme mismatch for an MCP server. It provides minimal value and does not justify a server deployment.
For the stated domain of greeting, the tool fully covers the intended action. There are no missing operations for such a trivial use case.