HelloWorld 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 |
|---|---|
| helloB | Say hello to someone |
| addA | Add two numbers together |
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 2 tools
The two tools have completely distinct purposes: 'add' performs a mathematical operation on numbers, while 'hello' handles a greeting interaction. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
Both tool names are simple, lowercase verbs ('add' and 'hello') that clearly indicate their actions. While they don't follow a strict verb_noun pattern, the naming is perfectly consistent in style and readability for this minimal set.
With only two tools, this server feels extremely thin and under-scoped for any meaningful domain. The tools are trivial and unrelated, suggesting either a demo/test server or one with significant missing functionality for practical use.
The server lacks a coherent domain, making completeness impossible to assess meaningfully. The tools are isolated operations (math and greeting) with no logical connection or coverage of any workflow, representing a severely incomplete surface for any real-world purpose.