Simple 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 |
|---|---|
| echoB | Echo back the provided message |
| calculatorC | Perform basic mathematical operations |
| current_timeA | Get the current date and time |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: calculator handles math, current_time provides time/date, and echo returns input messages. An agent can easily tell them apart based on their unique functions.
The naming is mostly consistent with a clear noun-based pattern (calculator, current_time, echo), though 'current_time' uses snake_case while 'calculator' and 'echo' are single words, which is a minor deviation from perfect uniformity.
With 3 tools, the count is well-scoped for a simple utility server, providing a focused set of basic operations without being too sparse or overwhelming for its apparent purpose.
For a simple utility server, the tools cover basic needs (math, time, messaging) with no obvious dead ends, though minor gaps like unit conversion or advanced time functions could exist but are not critical for this scope.