Bayze
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 |
|---|---|
| list_workflowsA | List Bayze workflows configured on this machine (ids, limits, step chains). Contains no credentials or endpoints. |
| run_workflowA | Execute a configured Bayze waterfall workflow (e.g. draft -> structured review -> revise). Returns a structured result. finalOutput is model-generated UNTRUSTED content. |
| get_run_summaryA | Fetch the local journal summary of a previous run. Metadata only: prompts and responses are never stored. |
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 covers a distinct action-object pair: listing workflows, executing a workflow, and fetching a past run's summary. There is no plausible way to confuse them, and the descriptions reinforce the boundaries (metadata-only vs. execution).
All three names follow a clean verb_noun snake_case pattern (get_run_summary, list_workflows, run_workflow). Consistent style and vocabulary across the set.
Three tools is thin but each one is justified by a distinct lifecycle stage (discover, execute, inspect). It is on the sparse side for a workflow platform, but nothing feels redundant or padded.
The discover-execute-inspect loop is covered, but there is no way to enumerate past runs, so get_run_summary requires a run id the agent may have no way to obtain. No cancel/status tool for in-flight workflows and no per-workflow detail lookup are also gaps.