mcp-starter
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_toolD | Hello tool |
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. The tool's purpose is clearly distinct by default.
The single tool name 'hello_tool' follows a consistent verb_noun pattern (hello + tool). With only one tool, consistency is inherently perfect.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. This feels thin and inadequate for typical MCP server use cases.
With only a 'hello_tool', the server lacks any meaningful domain coverage. It is severely incomplete, offering no operations for a coherent workflow or domain.