Skip to main content
Glama

Set inputs

set_inputs
Idempotent

Sets input values for an OpenMDAO problem, optionally in specified units, without saving them to the spec.

Instructions

Set input values, optionally in given units. Values set here are not persisted to the spec.

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

Input Schema

NameRequiredDescriptionDefault
unitsNoUnits per variable name, e.g. {'mass': 'kg'}.
valuesYesValues keyed by promoted variable name.
problem_idYes
allow_missingNo

Output Schema

NameRequiredDescriptionDefault
errorNo
skippedNo
updatedNo

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?

The idempotentHint annotation already communicates repeat-safe behavior, so the description is not starting from zero. It adds the useful and non-obvious fact that values are not persisted to the spec, but it omits overwrite behavior, session lifetime, error conditions, and how allow_missing affects behavior.

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?

The definition is two short sentences and is front-loaded with the core action. The non-persistence caveat follows immediately with no wasted wording.

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

Completeness2/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 explained. However, for a four-parameter tool with nested objects and only 50% schema coverage, the description is too thin: it leaves problem_id and allow_missing unexplained and does not cover key setting semantics.

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?

Schema description coverage is only 50%, and the description merely echoes units and values, which the schema already describes. It does not clarify the required problem_id or the meaning of allow_missing, leaving half the parameters semantically undocumented.

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: 'Set input values, optionally in given units.' It also adds the important scope note that values are not persisted to the spec. It does not explicitly differentiate the tool from related siblings such as update_problem, preventing a 5.

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?

The non-persistence note implies a temporary-override use case, but the description never states explicit when-to-use or when-not-to-use guidance. It also names no alternatives, leaving the agent to infer that update_problem might be the persistent counterpart.

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