hc0061365-mcp-hello-world
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| helloB | Say hello to someone. Returns a friendly greeting message. |
| greet_multipleC | Greet multiple people at once. |
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
hello targets a single recipient while greet_multiple targets multiple recipients, so the cardinality difference provides some distinction. However, greet_multiple is essentially a batch version of hello, creating overlap if an agent could simply call hello repeatedly.
hello is a bare greeting word while greet_multiple follows a verb+quantifier pattern; both are lowercase snake_case but do not follow a consistent verb_noun convention. The mixed structure is readable but not predictable.
Only two tools exist, which feels thin even for a hello-world server. The second tool is a minor variant rather than a distinct capability, so the set is borderline under-scoped.
The greeting domain is covered for single and multiple recipients, but there is no customization (e.g., formal/informal tone) or additional greeting lifecycle operations. These are minor gaps that an agent can work around.