Skip to main content
Glama

optimize_cmaes

Read-only

Optimize continuous parameters in non-convex, noisy, or gradient-free objectives using CMA-ES. Ideal for hyperparameter tuning, simulator calibration, and control policy optimization.

Instructions

[Premium] Continuous black-box optimization via CMA-ES (Covariance Matrix Adaptation Evolution Strategy). Use for tuning N continuous parameters when the objective is non-convex, noisy, or has no gradient — hyperparameter search, simulator calibration, control policy tuning. 10-100x fewer evaluations than grid search. For discrete combinatorial problems, use optimize_evolve. For LP/MIP problems with linear constraints, use solve_constraints. Stochastic init means re-runs with the same input may differ slightly. Requires ORACLAW_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dimensionYesNumber of parameters to optimize.
objectiveWeightsYesPer-dimension weight in the linear default objective. Length must equal dimension.
initialSigmaNoInitial step size (default: 0.5).
maxIterationsNoMax generations (default: 1000, capped at 5000).
initialMeanNoOptional starting point in parameter space.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bestSolutionYesBest parameter vector found.
bestFitnessYesObjective value at bestSolution (caller's sign convention).
iterationsYesGenerations actually run.
evaluationsNoTotal objective evaluations.
convergedYesWhether convergence criteria were met before maxIterations.
executionTimeMsNo
Behavior4/5

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

Discloses stochastic initialization leading to slight differences between runs, and the requirement for ORACLAW_API_KEY. Annotations already indicate non-destructive and read-only nature (readOnlyHint=true, destructiveHint=false), so description adds useful behavioral context without contradiction.

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?

Description is brief and front-loaded with key information (premium, continuous optimization, CMA-ES). Every sentence adds value, with no redundancy.

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?

Provides use cases, limitations, comparison to alternatives, stochastic behavior, and authentication requirement. Has output schema, so return values need not be explained. Complete for a complex optimization tool.

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 elaborate on parameter semantics beyond what the schema already provides, so no additional value added.

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 it performs continuous black-box optimization via CMA-ES, giving specific use cases (hyperparameter search, simulator calibration). It distinguishes itself from sibling tools (optimize_evolve for discrete, solve_constraints for LP/MIP).

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

Usage Guidelines5/5

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

Explicitly tells when to use (non-convex, noisy, gradient-free continuous optimization) and when not to (discrete or LP/MIP problems), with alternative tool names provided.

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/Whatsonyourmind/oraclaw'

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