Skip to main content
Glama

Load problem

load_problem
Idempotent

Rebuild a persisted OpenMDAO problem from its problem_spec.json after a server restart, restoring the saved model and driver setup for continued runs.

Instructions

Rebuild a persisted problem from its problem_spec.json (for example after a server restart).

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": "load_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
problem_idYes

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

A3.5/5.0
Behavior3/5

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

Annotations only declare idempotentHint=true, so the description carries the rest of the burden. It usefully discloses that state comes from a persisted problem_spec.json and the typical restart context, but says nothing about what happens if the ID does not exist, or whether an already-loaded in-memory problem is replaced or rejected.

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?

One short sentence, front-loaded with the verb and resource, then the mechanism and the ordering context. No filler or redundancy.

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 tool is low-complexity with a single parameter. Still missing is failure behavior (unknown or invalid ID) and any note on interaction with in-memory server state, which matters for a reload operation.

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%, so the schema only supplies a regex pattern, not meaning. The description partially compensates by implying the ID names a persisted problem with an associated problem_spec.json, but it does not say where that file lives or what form the ID takes.

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 ('Rebuild a persisted problem') and adds the mechanism ('from its problem_spec.json'), which distinguishes it from a plain create or read. It does not explicitly contrast with create_problem or get_problem_spec, but the verb 'rebuild' plus 'persisted' carves out a distinct scope.

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?

'for example after a server restart' gives an implied trigger condition, which is more than nothing. However it offers no exclusions (e.g. when the problem is already loaded in memory) and no explicit alternative for the case where a fresh problem is wanted rather than a reload.

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