ProBridge
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gpt56_pro_startA | Queue one verified GPT-5.6 Sol / Effort Pro Quick Chat sub-agent job for this MCP workspace. Returns immediately with a jobId. The local daemon serializes full job execution, verifies the UI send, and keeps authoritative lifecycle state outside the workspace. Poll gpt56_pro_status. |
| gpt56_pro_statusA | Read authoritative daemon state and the latest validated cooperative control-file report for a job in this MCP workspace. |
| gpt56_pro_followupA | Queue a follow-up in the verified same Quick Chat thread. The target must be the latest completed round and must have a captured chat title. Returns a child jobId; poll gpt56_pro_status. |
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 corresponds to one distinct lifecycle action: starting an initial job, polling its status, and queueing a follow-up to a completed thread. There is no meaningful overlap, even though start and followup both create work.
All tools share a clear gpt56_pro_ prefix and consistent lowercase snake_case formatting. Minor deviation: start and followup are verbs while status is a noun, but the action each tool performs is still highly predictable.
Three tools is well-scoped for the server's apparent purpose: launch a job, check status, and continue the conversation. Each tool earns its place, and no unnecessary tools inflate the surface.
The primary start-status-followup workflow is fully covered and workable. The main gaps are optional lifecycle conveniences like canceling a queued/running job or listing all active jobs, but agents can work around these.