Mock 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mock_echoB | Echo back the provided message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| mock_prompt | Generates a mock prompt for testing purposes. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_mock_data | Provides mock data for testing. |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'mock_echo' has a single, clear purpose of echoing messages, making it perfectly distinct.
The tool name 'mock_echo' follows a consistent verb_noun pattern (echo as the verb, implied message as the noun). Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.
A single tool is generally too few for most server purposes, as it limits functionality and suggests a trivial or incomplete scope. For a server named 'Mock MCP Server', which implies broader mocking capabilities, one tool feels insufficient and under-scoped.
The server's purpose is unclear from the name 'Mock MCP Server', but a single echo tool suggests severe incompleteness. It lacks coverage for common mocking operations like simulating data, errors, or varied responses, creating significant gaps that could cause agent failures in typical use cases.