teuton-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Show this server's name, version and data folder, and, for a server that needs programs installed apart, whether they're there. Contains no secrets. |
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
There is only one tool, so there is no possibility of confusion or misselection. Any agent asking for server metadata has exactly one target.
The single name 'server_info' is a clean noun-based identifier, but with only one tool there is no pattern to verify consistency against. It reads predictably and would fit a consistent resource_noun convention.
A single informational tool is very thin for an MCP server surface; there is essentially no workflow to support. It earns its place as a diagnostic, but one tool cannot be called well-scoped for a server identity like teuton-mcp.
For the narrow stated purpose of reporting name, version, data folder, and dependency presence, the tool is self-contained and complete. However, the surface offers no other operations, so any broader domain implied by the server name goes entirely uncovered.