CARBON Studio Pro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CARBON_STUDIO_HOME | No | Override the default state storage location (~/.carbon-studio-pro/workspace.json). |
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
} |
| resources | {
"listChanged": true
} |
| extensions | {
"openai/settings": {
"readTool": "settings.read",
"updateTool": "settings.update"
}
} |
| experimental | {
"openai/settings": {
"readTool": "settings.read",
"updateTool": "settings.update"
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| studio_openA | Open the CARBON Studio Pro visual quality workspace. Does not execute tests. |
| studio_preferencesC | Open the CARBON Studio Pro visual quality workspace. Does not execute tests. |
| studio_snapshotA | Read current runs, evidence, settings, and human steering. Poll this data tool rather than reopening the UI. sinceRevision avoids retransmitting unchanged snapshots. |
| studio_startC | Create a durable testing run for an explicitly selected local project. The coding agent must perform checks and report observations; this tool does not test the app itself. |
| studio_updateB | Record actual test observations, findings, progress, and concise decision rationale. Do not provide private chain of thought. Requires current run revision. |
| studio_screenshotC | Attach an actual PNG, JPEG, or WebP screenshot inside the selected project. No arbitrary file access. |
| studio_save_settingsC | Save testing preferences with optimistic concurrency protection. Budget values guide the agent; they are not hard host token limits. |
| studio_feedbackB | Read or save personal report feedback for this OS account and project. Hiding never alters test evidence or confidence. Read returned preferences before further investigations. |
| studio_steerB | Persist user guidance on a finding. The agent reads it before selecting the next check. |
| settings.readD | – |
| settings.updateD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| CARBON Studio Pro |
TDQS
Scored across 11 tools
studio_open and studio_preferences share an identical description, making them indistinguishable, and studio_save_settings, settings.update, and settings.read all appear to write the same preferences. studio_feedback vs studio_save_settings also overlap. Several tools have unclear boundaries despite good individual descriptions elsewhere.
Eight tools use a consistent studio_verb/noun snake_case pattern, but settings.read and settings.update break the convention with dot notation and no studio prefix. Mixing two naming schemes on a single server is a clear inconsistency.
11 tools is a reasonable scope for a testing workspace lifecycle. However, the presence of redundant pairs (open/preferences, save_settings/settings.update) inflates the count slightly beyond what is earned.
The surface covers the full run lifecycle: opening the workspace, starting a run, snapshotting state, recording observations, attaching screenshots, saving settings, feedback, and steering. Main gap is that settings read/update duplicate existing functionality rather than filling a real hole.