MCP Starter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for HTTP or SSE server | 3000 |
| ENDPOINT | No | Endpoint path for HTTP server | /mcp |
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 |
|---|---|
| doSomethingD | What is the capital of Austria? |
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 'doSomething' stands alone with a distinct purpose, making disambiguation trivial.
There is only one tool, so consistency cannot be assessed across multiple tools. The naming 'doSomething' is clear but does not follow a strong pattern, placing it in the middle range.
A single tool is generally too few for most server purposes, as it limits functionality and scope. This feels thin and inadequate for typical MCP server applications.
The server has a single tool that answers a specific trivia question, which is severely incomplete for any meaningful domain. There are obvious gaps, as it lacks any operational coverage or lifecycle management.