rote
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rote_list_pipelinesA | List every compiled pipeline this server can trigger: its name, description, runtime, where its trigger points, and the names of its trigger, status, and (dbos only) signal tools. Reads the registry file on each call, so pipelines added by rote register show up immediately. An empty or missing registry returns an empty list rather than an error. |
| rote_describe_pipelineA | Return one registered pipeline's full registry entry: the JSON Schema its trigger tool accepts, its runtime trigger configuration with any URL passwords redacted, and its trigger, status, and signal tool names. Fails with the list of registered names when the name is unknown. |
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 2 tools
The two tools have clearly distinct purposes: one lists all pipelines, the other describes a single pipeline in detail. There is no overlap or ambiguity between them.
Both tools follow the same predictable pattern: `rote_` prefix followed by a verb and noun (`rote_list_pipelines`, `rote_describe_pipeline`). The convention is consistent and readable.
Only two tools are provided, which is too few for a server that can trigger pipelines and manage their lifecycle. The descriptions imply trigger, status, and signal tools exist, but they are absent, making the set severely under-scoped.
The surface only covers listing and describing pipelines, but the core operations of triggering, checking status, and sending signals are missing. This is a significant gap that will prevent agents from completing actual pipeline workflows.