Skip to main content
Glama

Run multi-start

run_multistart

Run multi-start optimization by sampling designs with LHS, keeping the top feasible seeds, then locally optimizing each seed, optionally across parallel workers.

Instructions

Multi-start optimization: LHS sampling, keep the top_k feasible seeds, then a normalized local optimization (SLSQP by default) from each, in spawn worker processes when n_workers > 1.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "problem_id": "<problem_id>",
      "n_samples": "<n_samples>",
      "top_k": "<top_k>"
    },
    "name": "run_multistart"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
top_kYes
n_samplesYes
n_workersNo
optimizerNo
problem_idYes
auto_normalizeNo
feasibility_tolNo

Output Schema

NameRequiredDescriptionDefault
bestNo
runsNo
errorNo
messagesNo
n_sampledNo
captured_outputNo
n_feasible_seedsNo
doe_recorder_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With only a title annotation, the description carries the full burden, and it does disclose real behavior: sampling, feasibility filtering, normalization, local optimization, and process spawning when n_workers > 1. It omits important traits such as whether the problem's state is mutated, expected runtime/cost, determinism from seed, and error behavior when too few feasible seeds exist.

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?

A single dense sentence that front-loads the operation name and then walks the pipeline in execution order. No filler, though the packed clause structure makes it slightly harder to scan than a short bulleted flow.

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?

An output schema exists, so return values need no explanation, and the pipeline narrative covers the core mechanics. For an 8-parameter optimization tool with zero schema descriptions, though, it leaves too many parameters and the state-mutation question unanswered.

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 0% across 8 parameters, so the description must compensate. It adds meaning for top_k (seeds retained), n_workers (spawned processes), and the optimizer default (SLSQP), but leaves n_samples, seed, auto_normalize, feasibility_tol, and problem_id entirely unexplained.

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

Purpose4/5

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

The description states a specific verb and resource — multi-start optimization — and sketches the algorithm (LHS sampling, top_k feasible seeds, normalized local optimization), which is distinctive enough to separate it from run_driver and run_doe. It stops short of naming those siblings explicitly, so differentiation is inferred from the algorithm rather than stated.

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?

There is no when-to-use guidance: nothing says when multistart is preferable to run_driver, run_doe, or configure_optimization, nor what prerequisites (a configured problem with objectives/constraints) must exist first. Usage is only implied by the algorithmic sketch.

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