shinyprobe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHINYPROBE_HEADED | No | Set to '1' to run the browser in headed mode (watch the browser). | |
| SHINYPROBE_PYTHON | No | Path to the python executable to use for Python apps. If not set, uses python on PATH. | |
| SHINYPROBE_RSCRIPT | No | Path to the Rscript executable to use for R apps. If not set, uses Rscript found on PATH or default install folder on Windows. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| launch_appA | Start the Shiny app at
|
| attachB | Open an app that is already running (local or deployed) at |
| stop_appB | Close the browser page and, for launched apps, stop the app process. |
| list_controlsA | List every input (id, type, label, current value, choices, visible) and output (id, type, status, visible). Call again after dynamic UI changes: the page is re-scanned every time. |
| set_inputsA | Set one or more inputs, e.g. {"n": 5, "species": ["setosa"]}, through their widgets, then wait for the app to settle. Warns if an input ends up with a different value than asked for. Use click for buttons and upload_file for file inputs. |
| clickA | Click the element with this id (usually an action button), then wait for the app to settle. If it is on another tab or in a closed panel, those are opened first, as a user would. |
| showA | Bring an element into view: |
| upload_fileB | Upload the local file at |
| read_outputsA | Read outputs (all of them when |
| get_errorsA | Every error seen so far: server errors with traces (and the output they broke), Shiny output errors, browser console errors, and the app exiting. With since_last=True, only errors since the previous since_last call. |
| get_consoleA | The app's console output (print, message, cat, logging), newest last: the last |
| screenshotA | Take a PNG screenshot of the whole page, or of one element when |
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 12 tools
Every tool targets a distinct action: lifecycle (attach, launch_app, stop_app), UI inspection (list_controls), interaction (set_inputs, click, show, upload_file), output reading (read_outputs), and diagnostics (get_errors, screenshot, get_console). No two tools overlap in purpose, making misselection highly unlikely.
All names follow a consistent verb_noun pattern in snake_case (e.g., launch_app, set_inputs, read_outputs). Single verbs like attach and click are still clear and fit the pattern, with no mixed conventions or vague terms.
12 tools is well-scoped for a Shiny app interaction server. Each tool covers a necessary capability for starting, controlling, inspecting, and debugging apps, without redundancy or bloat.
The surface covers the full lifecycle from launch to stop, all common input interactions, output reading, and error/console diagnostics. No obvious gaps exist for typical Shiny testing workflows, making the set self-sufficient.