Skip to main content
Glama
alexalexalex222

super-loop-mcp

run_campaign

Runs a self-supervised campaign that mines past sessions, improves workflows, and verifies each output through multiple frontier workers, rejecting invalid batches until benchmarks pass.

Instructions

AUTONOMOUS SUPERVISOR (opt-in: SUPER_LOOP_ALLOW_EXEC=1). One call drives the whole campaign itself — intake → work the target queue (mine → improve) → for each improve target: hash-lock baseline → freeze benchmark → measure the bar on a real worker → FullTestBatches (3-5 frontier workers, each output VALIDATED through the enforcement boundary) → supervisor delta → reverify → promote (bank a Stone) → advance/retire → re-mine — and keeps going until the operator stop-file. Worker output is never trusted: summary-only / early-stop / fake-metric / self-promote / phase-skip / copied-public are rejected and re-entered, and invalid batches do not count toward retirement. maxBatches bounds the in-call MCP run (a safety cap, NOT completion); the standalone super-loop-run CLI runs it until the stop-file. Returns the exact string MISSING_FULL_PRIVATE_LOOPS if a full private loop is absent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYes
configYes{ task, routes:[3-5 frontier], benchmark:{name,taskValueDimensions,resourceDimensions,cases,oracle}, targets:[{kind:"mine"|"improve", loop?, baselineContent?, benchmark?, routes?}], noImprovePolicy?(default 30), remineOnEmpty? }
stopFileNopath whose existence stops the campaign — the operator stop signal
maxBatchesNosafety cap on valid FullTestBatches for this in-call run (default 3); not a completion state
Behavior5/5

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

No annotations provided, so description carries full burden. It exhaustively discloses the pipeline steps, security measures (worker output never trusted, rejection of invalid batches), return value (MISSING_FULL_PRIVATE_LOOPS), opt-in requirement, and the role of maxBatches as an in-call safety cap. No behavioral contradictions.

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

Conciseness4/5

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

The description is long but every sentence adds necessary detail for a complex tool. It is front-loaded with 'AUTONOMOUS SUPERVISOR' and uses bullet-like flow with arrows. Could be slightly more structured but remains efficient.

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

Completeness5/5

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

Covers all essential aspects: pipeline steps, validation rules, safety cap, stop-file mechanism, return value, and opt-in requirement. No output schema exists, but the description fully compensates by explaining the only return string. Complete for a tool of this complexity.

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

Parameters4/5

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

Schema description coverage is 75%, and the description adds value by explaining the 'config' parameter's nested structure and clarifying 'stopFile' and 'maxBatches' semantics beyond the schema. However, 'runId' lacks both schema description and description text.

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 that this tool 'drives the whole campaign itself' and outlines the full pipeline. It distinguishes itself from sibling tools like 'campaign_status' and 'continue_run' by being the autonomous supervisor that handles intake, work, validation, and retirement until a stop-file.

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?

Provides explicit opt-in condition (SUPER_LOOP_ALLOW_EXEC=1) and contrasts with the standalone CLI alternative. Explains maxBatches as a safety cap rather than completion. Does not directly compare to sibling tools but the autonomous nature is clear.

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/alexalexalex222/super-loop-mcp-merged'

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