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 |
|---|---|
| hello_worldC | A simple hello world tool that returns a greeting. |
| get_versionB | Get server version information. |
| system_infoB | Get basic system information. |
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
All three tools have clearly distinct purposes with no overlap: get_version retrieves server metadata, hello_world provides a customizable greeting function, and system_info returns hardware/OS information. An agent could easily distinguish between these different domains.
Two tools follow a consistent verb_noun pattern (get_version, system_info), while hello_world uses a different convention. The deviation is minor since all names remain clear and readable, but the pattern isn't fully uniform.
With only three tools, this feels somewhat thin for a general-purpose server. While each tool serves a distinct function, the set lacks depth and could benefit from additional utilities to form a more complete toolkit.
The server's purpose appears to be general system/server utilities, but there are significant gaps: no file operations, no network utilities, no process management, and no configuration tools. The three existing tools provide only basic informational functions without supporting common workflows.