MCP Workshop 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 |
|---|---|
| get-igorC | When somebody asks for or mentions Igor |
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 between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The tool name 'get-igor' follows a verb-noun pattern, which is straightforward.
One tool is generally too few for a server's purpose unless it's extremely narrow, but the tool description suggests a trivial or joke functionality ('When somebody asks for or mentions Igor'), which feels insufficient for a meaningful server scope. This mismatch makes the count inappropriate.
The server's domain is unclear from the single tool, but the tool 'get-igor' appears to be a trivial or humorous response mechanism. There are obvious gaps as no meaningful operations or lifecycle coverage are provided, making the surface severely incomplete for any practical purpose.