MCP Tool Starter Kit
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 |
|---|---|
| getUserInfoC | Fetches user information from an API |
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 ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'getUserInfo' follows a clear verb_noun pattern.
A single tool is too few for a server named 'MCP Tool Starter Kit', which implies a broader or introductory set of tools. This minimal count feels incomplete and mismatched with the expected scope.
The tool surface is severely incomplete; 'getUserInfo' alone cannot cover any meaningful domain or workflows. There are significant gaps, such as lacking create, update, delete, or other related operations, making it inadequate for practical use.