Modular MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Control log level. Valid values: ERROR, WARN, INFO, DEBUG | INFO |
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 |
|---|---|
| echoA | Echo back the input (useful for testing) |
| calculateB | Perform a mathematical calculation (safe eval) |
| timestampB | Get current timestamp |
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: calculate handles math operations, echo returns input for testing, and timestamp provides the current time. There is no ambiguity or confusion between these three functions.
All tool names follow a consistent pattern of using single, descriptive words (calculate, echo, timestamp) without mixing conventions like camelCase or snake_case. This uniformity makes the set predictable and easy to understand.
With only 3 tools, the server feels thin and limited in scope, potentially lacking coverage for broader utility needs. While each tool is distinct, the count is borderline low for a general-purpose utility server, suggesting it might be under-scoped.
The tools cover basic utility functions (math, testing, time), but there are notable gaps for a modular server, such as missing data transformation, file handling, or network operations. This limits the server's ability to handle more complex agent workflows effectively.