autoevolve
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | API key for a cloud OpenAI-compatible endpoint. Used with AUTOEVOLVE_MODEL. Alternative to local configuration. | |
| OPENAI_BASE_URL | No | Optional base URL for cloud endpoint. Defaults to OpenAI's API. | |
| AUTOEVOLVE_MODEL | No | Model name to use for cloud endpoint. Required when OPENAI_API_KEY is set. | |
| AUTOEVOLVE_LOCAL_BASE_URL | No | Base URL for a local OpenAI-compatible engine. No API key needed. Alternative to cloud configuration. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_runA | Open and lock an evolution run for a measured goal. |
| get_contractA | Read the immutable scoring contract before doing worker work. |
| join_runA | Join a run and receive this worker's island assignment. |
| next_parentA | Get the parent and evidence needed for one mutation cycle. |
| submit_childA | Submit full child file contents for evaluation and archive insertion. |
| bestA | Read the best measured programs in a run. |
| lineageA | Read the recorded ancestry for one evaluated program. |
| discoveriesA | Search reusable measured discoveries for a domain. |
| run_statusA | Read closure state, progress, budget, and artifact paths for a run. |
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 9 tools
Each tool serves a distinct, non-overlapping role in the evolution workflow: run lifecycle (open_run, join_run, run_status), contract access (get_contract), mutation cycle (next_parent, submit_child), and result/history lookup (best, lineage, discoveries). There is no ambiguity about which tool to use for a given task.
Naming mixes verb-noun forms (open_run, get_contract, join_run, submit_child) with noun-only (lineage, discoveries), adjective-noun (next_parent), and noun-noun (run_status). While all names use lowercase_with_underscores and are descriptive, the lack of a consistent pattern makes tool names less predictable.
Nine tools is well-scoped for the server's purpose. Each tool covers a necessary step in the evolutionary run lifecycle without redundancy or bloat, fitting comfortably in the typical 3-15 range.
The tool set provides complete coverage for an evolution run: creation, contract inspection, joining, mutate/submit cycle, status monitoring, and outcome retrieval. No critical operations are missing; lifecycle end is handled via run_status and Engine state.