Skip to main content
Glama

ouroboros_auto

Automates interviews, generates an A-grade Seed, and executes only after passing the A-grade gate, with all loops bounded.

Instructions

Run full-quality ooo auto: automatically interview, generate an A-grade Seed, and start execution only after the A-grade gate passes. All loops are bounded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory
goalNoGoal/task for ooo auto
domainNoOptional domain profile name (for example, coding)
resumeNoAuto session id to resume
skip_runNoStop after A-grade Seed
attach_jobNoAttach an externally verified job id to an unknown run handoff
attach_sourceNoSource label for an attached run handle
commit_policyNoCheckpoint commit policy: ac_checkpoint, final_only, or none
reconcile_runNoTry to reconcile an unknown run handoff without starting a duplicate run
attach_sessionNoAttach an externally verified run session id to an unknown run handoff
efficiency_modeNoExecution efficiency policy: adaptive may use lower-cost child tiers with recovery escalation; quality_first keeps child ACs at the parent starting tier. Default: adaptive.
worktree_policyNoWorktree isolation policy: auto, always, current, or none
attach_executionNoAttach an externally verified execution id to an unknown run handoff
complete_productNoWhen true, chain RUN → RALPH_HANDOFF after a successful run handoff so a single ouroboros_auto invocation iterates Ralph until QA passes, convergence, or a budget bound trips. Defaults to false (opt-in).
reconcile_sourceNoSource label for run handoff reconciliation
user_preferencesNoCaller-supplied user preferences keyed by ledger section name (e.g. runtime_context, constraints, non_goals). The Driver tags matching answers with [from-auto][user_preference] in the ledger. Keys must be valid ledger section names; values must be non-empty strings or non-empty lists of strings/numbers. On resume, null/empty values clear the persisted preference for that section.
max_repair_roundsNoMax repair rounds
frugality_assuranceNoFrugality assurance: off, observe, or explicitly authorized strict. Defaults from efficiency_mode and is immutable on resume.
max_interview_roundsNoMax interview rounds
pipeline_timeout_secondsNoTop-level pipeline deadline in seconds. Defaults to 7200s for new sessions. Range: 60-86400. Cannot be changed on resume; the deadline is preserved across process restarts.
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description adds some behavioral context: the A-grade gate blocks execution until quality is met, and all loops are bounded. However, it does not detail side effects, runtime expectations, or interaction with resume/attach options, leaving a gap for such a complex tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the main purpose and followed by a key safety guarantee. It is appropriately concise, leaving parameter details to the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (20 parameters, nested options) and no output schema, the description gives the essential pipeline overview but omits broader context like resume/attach/reconciliation workflows. However, the schema covers parameter details thoroughly, so the combination is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description itself does not elaborate on any parameters, providing no additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Run') and names the resource/pipeline (full-quality ooo auto). It enumerates the key steps (interview, generate A-grade Seed, execute after gate) which distinguishes it from simpler siblings like execute_seed or start_auto.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys a clear context: this is the complete automatic pipeline with a quality gate. It does not explicitly mention alternatives or exclusions, but the workflow description implies when to use it (for full auto runs).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Q00/ouroboros'

If you have feedback or need assistance with the MCP directory API, please join our Discord server