Hello-MCP
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addD | – |
| send-emailD | – |
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, 'add' and 'send-email', have no descriptions and appear to serve completely unrelated purposes. An agent cannot determine what 'add' refers to or how it relates to sending email, creating ambiguity.
The tool names follow no consistent pattern: 'add' is a bare verb while 'send-email' uses a verb-noun format with a hyphen. The lack of a shared convention makes the set feel ad hoc.
With only two tools and no descriptions, the server appears extremely thin and under-scoped. It is unclear what domain it covers, and two unrelated tools do not form a coherent toolkit.
The server's purpose is entirely unclear from the tool names alone. 'add' and 'send-email' do not suggest any complete workflow or domain coverage, leaving obvious gaps in any conceivable use case.