MCPKit
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetD | – |
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 in the server, there is no possibility of overlap or confusion between tools. The agent does not need to distinguish competing operations.
The single tool name 'greet' uses a clear lowercase verb with no conflicting naming style. However, one tool is too few to establish a meaningful naming pattern across a server.
A server named MCPKit containing only one trivial tool is severely underprovisioned. This tool count earns no place in a coherent server surface.
The only tool, 'greet', provides a trivial single action with no description and no supporting operations. The server surface is severely incomplete for any plausible broader purpose.