MCP Demo
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hackathon_infoA | Get the complete hackathon overview with all information about the MCP Server Hackathon. Returns: The full hackathon overview document including format, getting started guide, project ideas, resources, and quick reference. |
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 between tools. The purpose is clearly defined and unique.
The single tool name 'get_hackathon_info' follows a clear verb_noun convention, which is internally consistent.
A single tool feels thin for a server, even as a demo. It is borderline but not necessarily inappropriate given the focused purpose.
The tool fully covers the stated purpose of retrieving hackathon information. There are no obvious missing operations for this narrow scope.