Skip to main content
Glama

Run model

run_model

Evaluate an OpenMDAO model once after optionally setting promoted inputs, returning requested outputs, success status, and nonlinear-solver convergence.

Instructions

Evaluate the model once, optionally after setting inputs. A failed evaluation (AnalysisError) returns success=false instead of an error; converged reports nonlinear-solver convergence.

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>"
    },
    "name": "run_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoValues keyed by promoted variable name.
outputsNoPromoted names of outputs to return.
problem_idYes

Output Schema

NameRequiredDescriptionDefault
errorNo
outputsNo
successNo
messagesNo
convergedNo
elapsed_sNo
failure_kindNo
captured_outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full behavioral burden. It does add genuinely valuable context: a failed evaluation surfaces as success=false rather than an exception, and converged reflects nonlinear-solver convergence. It omits whether inline inputs mutate persisted problem state, whether the call is read-only with respect to the problem, and whether there are cost or timeout characteristics.

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?

Two short sentences with zero filler; the core action is front-loaded and the error-behavior caveat follows. Every clause carries information an agent would otherwise have to discover by trial.

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

Completeness4/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 not be enumerated, and the description covers the one surprising return case (success=false on AnalysisError). For a three-parameter tool with a nested inputs object, the main remaining gap is side-effect disclosure about problem state.

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 67%, so most parameters are documented in the schema already. The phrase "optionally after setting inputs" adds real meaning about the inputs parameter (values applied before evaluation), but the outputs parameter is not explained beyond its schema text, and the interaction between inputs and prior set_inputs calls is unstated.

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?

"Evaluate the model once" gives a specific verb and resource, and the word "once" implicitly distinguishes it from multi-run siblings like run_doe, run_driver and run_multistart. It does not name an alternative explicitly, so an agent must infer the boundary from the sibling names rather than from the description.

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

Usage Guidelines3/5

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

"optionally after setting inputs" implies this tool can replace a separate set_inputs call by passing values inline, which is useful implied guidance. However, there is no explicit statement of when to choose run_model over run_doe or run_driver, and no prerequisites or exclusions are stated.

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