Skip to main content
Glama

Create problem

create_problem

Build an OpenMDAO problem from a declarative ProblemSpec covering components, groups, solvers, variables, objective, constraints, and driver, then persist it as problem_spec.json.

Instructions

Build an OpenMDAO problem from a declarative ProblemSpec (components, nested groups, solvers, design variables, objective, constraints, driver) and persist it as problem_spec.json.

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": {
      "spec": "<spec>"
    },
    "name": "create_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
run_setupNo
problem_idNo

Output Schema

NameRequiredDescriptionDefault
nameNo
errorNo
inputsNo
statusNo
outputsNo
workdirNo
warningsNo
objectiveNo
problem_idNo
constraintsNo
design_varsNo
n_subsystemsNo
captured_outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No behavioral annotations exist, so the description carries the full burden. It does disclose one important side effect (persisting problem_spec.json), but is silent on whether the model is actually built/validated, what happens if a problem with the same name or problem_id already exists, where files are written, and whether the operation is idempotent.

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 front-loaded sentence with no filler; the verb+resource comes first and the input/output artifacts follow. The long parenthetical is dense but each item is informative rather than redundant.

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 nested ProblemSpec schema documents most sub-objects. Still missing for a tool of this complexity are the meaning of run_setup, problem_id reuse/collision behavior, and where problem_spec.json lands.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema description coverage is 0%, and two of the three parameters (run_setup, problem_id) are never mentioned, even though run_setup=true implies real build/validation work and problem_id implies collision semantics. The description does summarize the contents of 'spec', partially compensating for that one parameter.

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?

States a specific verb and resource ('Build an OpenMDAO problem') plus an explicit input artifact ('a declarative ProblemSpec') and an output side effect ('persist it as problem_spec.json'). This distinguishes it from load_problem and update_problem, though the description never names those siblings.

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?

Usage is only implied: an agent can infer this is the entry point that materializes a spec into a new problem, and the parenthetical enumerates what the spec covers. There is no explicit when-to-use, when-not-to-use, or pointer to load_problem/update_problem for the modify-existing case.

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