Skip to main content
Glama

run_autoresearch

Destructive

Automate bounded metric improvement by testing hypotheses, requiring primary and holdout checks, and retaining only proven candidate mutations.

Instructions

Run a bounded metric-improvement loop: measure a baseline, test a hypothesis, require primary and holdout checks, then keep or discard the candidate mutation with proof.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iterationsNoNumber of iterations to run. Capped at 5 per call; default 1.
targetNameNoOptional evolution target to mutate.
nextValueNoOptional explicit candidate value for the target.
testCommandNoPrimary metric command. Defaults to npm test.
holdoutCommandsNoAdditional checks required before a candidate can be kept.
timeoutMsNoPer-command timeout in milliseconds. Capped at 600000; default 120000.
cwdNoOptional workspace directory for the evaluation commands.
researchQueryNoOptional research query used to build an autoresearch context brief.
paperLimitNoMaximum research papers to ingest when researchQuery is set. Capped at 10; default 5.
Behavior3/5

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

Annotations indicate destructiveHint=true, so description correctly implies mutation. It adds that loops are bounded (capped iterations) and mentions safety limits (timeout caps). However, it does not detail what exactly gets mutated or destroyed, nor the implications of destructive behavior.

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?

Single concise sentence that encapsulates the workflow. It is front-loaded and direct, but could be split for readability. No wasted words.

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

Completeness3/5

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

No output schema is provided. The description omits what the tool returns, how results are presented, and whether it outputs logs or a summary. For a tool that runs multiple iterations, this is a gap. The parameter descriptions are complete, but the overall behavioral contract is incomplete.

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 coverage is 100%, so baseline is 3. The description does not add any new parameter information beyond what the schema provides. It restates the function of the tool but does not elaborate on parameter interactions or constraints.

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?

Description clearly states the tool runs a bounded metric-improvement loop with specific steps (measure baseline, test hypothesis, require checks, keep/discard). It distinguishes from sibling tools which are mostly about feedback, context, or governance, not automated optimization.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. The description only explains what it does, not the context or prerequisites for using it over other sibling tools like run_harness or plan_* tools.

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/IgorGanapolsky/ThumbGate'

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