WinTerm 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 |
|---|---|
| write_to_terminalC | Write text or commands to the terminal |
| read_terminal_outputC | Read the output from the terminal |
| send_control_characterC | Send a control character to the terminal |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: reading output, sending control characters, and writing text/commands are three separate terminal operations. An agent can easily tell them apart based on their specific functions.
All tools follow a consistent verb_noun pattern (read_terminal_output, send_control_character, write_to_terminal) with snake_case throughout. The naming is predictable and readable across the set.
Three tools is slightly thin but reasonable for a terminal-focused server, covering core input/output and control operations. It feels minimal but not incomplete, as each tool earns its place for basic terminal interaction.
The tools cover the essential terminal operations: reading, writing, and control. A minor gap might be the lack of a tool for managing terminal sessions or configuration, but for basic interaction, the surface is largely complete without dead ends.