otto
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| terminal_statusA | Situational awareness entry point. Returns terminal health plus the Command Center summary: current milestone, goal status, active task, risk gates (live/secrets), recovery count, and provider freshness. Call this first before operating. |
| list_routesA | List the 15 terminal routes with their route_id, label, category, and primary endpoint. Use route_id with get_route. |
| get_routeA | Fetch the current state of one route (e.g. dashboard, markets, portfolio, backtest, command center is under settings). Returns the route's primary read-only payload. |
| list_actionsA | List the safe operable actions (from the terminal agent-contract). Excludes safety-disabled and secret actions. Each row shows action_id, route_id, label, method, endpoint, request_contract, safety_class, whether it mutates local state, and whether it needs confirmation. Use action_id with run_action. |
| run_actionA | Execute one safe terminal action by action_id (from list_actions). Refuses safety-disabled and secret actions. For POST actions pass 'body'; for endpoints with {placeholders} pass 'path_params'; optional 'query'. If the action requires confirmation, pass confirm=true. |
| refresh_public_dataA | Convenience: start the public no-key provider refresh job and return its result summary (written / available / reused cache counts). This is the common 'load fresh public data' operation; no keys or private accounts. |
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 6 tools
Each tool has a clearly distinct purpose: fetching a route, listing actions, listing routes, refreshing data, executing an action, and checking terminal status. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_route, list_actions, run_action). This makes them predictable and easy to understand.
Six tools is well-scoped for a terminal interface. Each tool serves a necessary function without redundancy, covering status, navigation, data refresh, and action execution.
The tool surface covers key operations: status, listing resources, fetching data, refreshing public data, and executing actions. Minor potential gaps like direct search or filtering are not critical given the design.