my-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| helloB | A simple greeting tool that returns a hello message. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to disambiguate from. The tool's purpose is clearly distinct by default in this minimal set.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare against or create patterns with. The name 'hello' is straightforward and follows a simple verb-like convention without deviation.
A single tool is generally too few for most server purposes, as it offers very limited functionality and scope, making it feel thin and inadequate for handling typical tasks or workflows in a domain. This server appears to be a trivial example rather than a practical toolset.
The server's purpose is unclear from the single tool, but for any inferred domain (e.g., greeting or basic interaction), the surface is severely incomplete—it lacks any CRUD operations, lifecycle coverage, or meaningful workflows, making it impossible for agents to perform substantive tasks.