brainfaq-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 |
|---|---|
| load_codeB | Reset the debugger and load new Brainfuck source code. |
| stepC | Execute a specific number of instructions (default 1). Then outputs the summary of the current state. |
| runB | Run the program until it finishes or waits for input. Infinite loops WILL hang the server. Then outputs the summary of the current state. |
| add_inputA | Append characters to input buffer. Use when status is WAITING_FOR_INPUT. Outputs the engine status. |
| get_stateA | Get the current full state (memory, pointers, output). When windowRadius is not specified, returns the entire tape which may be a large amount of data. |
| read_outputA | Get the full output string generated so far. |
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 6 tools
Each tool has a clear, distinct purpose: loading code, stepping, running, input/output, and state inspection. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (add_input, get_state, load_code, read_output, run, step), with the exception of 'step' which is a verb but fits the pattern.
6 tools is well-scoped for a Brainfuck debugger/interpreter, covering all essential operations without unnecessary bloat.
The tool set covers the core workflow (load, step, run, input, output, state) but lacks an explicit stop/interrupt mechanism, which is a minor gap given the warning about infinite loops.