EpicMe MCP
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 |
|---|---|
| echoC | 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 |
| getResourceLinksC | Returns multiple resource links that reference different types of resources |
| structuredContentC | Returns structured content along with an output schema for client data validation |
| zipB | Compresses the provided resource files (mapping of name to URI, which can be a data URI) to a zip file, which it returns as a data URI resource link. |
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 11 tools
Multiple tools have overlapping or unclear purposes. For example, 'annotatedMessage', 'structuredContent', and 'getResourceLinks' all seem to demonstrate metadata or structured data features, making it difficult for an agent to choose between them. Similarly, 'echo' and 'printEnv' both serve debugging purposes, while 'add' and 'zip' are isolated utilities with no clear connection to the others.
The naming conventions are inconsistent and chaotic. There is a mix of styles: some tools use camelCase (e.g., 'annotatedMessage', 'getResourceLinks'), others use snake_case (e.g., 'longRunningOperation', 'printEnv'), and some are single words (e.g., 'add', 'echo', 'zip'). There is no discernible pattern, which makes the set harder to navigate and predict.
With 11 tools, the count is reasonable for a server, but it feels borderline due to the lack of a clear domain. The tools appear to be a miscellaneous collection of demonstrations and utilities rather than a cohesive set for a specific purpose, making the number seem slightly high for the apparent scope.
The server lacks a clear domain, making it difficult to assess completeness. However, based on the tool descriptions, it seems to be a demonstration server for MCP features. There are significant gaps: for example, if it's meant to showcase MCP capabilities, it might miss tools for other core features like streaming or error handling. The tools are fragmented and don't form a complete workflow or coverage of a specific area.