HPC-MCP
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 |
|---|---|
| debug_crashC | Debug crashing program and return the stack trace. |
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, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect—there are no other tools to create inconsistency or mixed conventions. The tool name follows a clear verb_noun pattern.
A single tool is too few for a server named 'HPC-MCP', which suggests a High-Performance Computing domain that typically involves complex workflows like job submission, monitoring, and resource management. This minimal toolset severely limits functionality.
The tool surface is severely incomplete for an HPC domain; it only provides a debug function, missing essential operations such as job submission, status checking, file management, and resource allocation, which are core to HPC workflows.