MCP Elicitations Demo 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoB | Echoes back the input! |
| addB | Adds two numbers |
| longRunningOperationC | Demonstrates a long running operation with progress updates |
| printEnvA | Prints all environment variables, helpful for debugging MCP server configuration |
| sampleLLMC | Samples from an LLM using MCP's sampling feature |
| getTinyImageC | Returns the MCP_TINY_IMAGE |
| annotatedMessageC | Demonstrates how annotations can be used to provide metadata about content |
| getResourceReferenceC | Returns a resource reference that can be used by MCP clients |
| startElicitationB | Demonstrates the Elicitation feature by asking the user to provide information about their favorite color, number, and pets. |
| getResourceLinksC | Returns multiple resource links that reference different types of resources |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| simple_prompt | A prompt without arguments |
| complex_prompt | A prompt with arguments |
| resource_prompt | A prompt that includes an embedded resource reference |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Resource 1 | |
| Resource 2 | |
| Resource 3 | |
| Resource 4 | |
| Resource 5 | |
| Resource 6 | |
| Resource 7 | |
| Resource 8 | |
| Resource 9 | |
| Resource 10 |
TDQS
Scored across 10 tools
The tools have distinct technical purposes, but there is some functional overlap in the demonstration category. For example, 'annotatedMessage', 'longRunningOperation', 'sampleLLM', and 'startElicitation' all serve as MCP feature demos, which could cause confusion about which to use for general demonstration tasks. However, their specific descriptions help differentiate them.
The naming conventions are inconsistent, mixing verb-first (e.g., 'add', 'echo', 'printEnv'), noun-first (e.g., 'annotatedMessage'), and descriptive phrases (e.g., 'longRunningOperation', 'getResourceLinks'). There is no uniform pattern like verb_noun or camelCase throughout, making the set less predictable.
With 10 tools, the count is reasonable for a demo server showcasing various MCP features. It is well-scoped to demonstrate capabilities without being overwhelming, though it might feel slightly heavy if the purpose is purely educational rather than functional.
As a demo server, the tool set comprehensively covers the intended domain of MCP feature demonstrations, including basic operations, resource handling, long-running tasks, LLM sampling, and elicitations. There are no obvious gaps for its stated purpose of showcasing MCP functionalities.