Test 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoB | Echo back the input text |
| add_numbersB | Add two numbers together |
| get_system_infoC | Get basic system information |
| validate_emailC | Validate an email address format |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Example Text File | A sample text file resource |
| Example JSON File | A sample JSON file resource |
TDQS
Scored across 4 tools
Each tool targets a completely different operation: text echo, arithmetic, system introspection, and email validation. There is no plausible way an agent could confuse one for another.
Three tools follow a clear verb_noun snake_case pattern (add_numbers, get_system_info, validate_email), while 'echo' is a bare verb with no object. The single deviation is minor and still unambiguous.
Four tools is a thin but defensible surface for a test/demo server, and each tool exercises a distinct capability. It would feel under-scoped for a real utility server, but fits the stated testing purpose.
The toolset is an arbitrary grab bag of unrelated utilities with no defined domain, so there is no lifecycle to complete. No obvious dead ends exist, but there is also no coherent surface an agent could rely on beyond these four one-off operations.