Skip to main content
Glama

Get outputs

get_outputs
Read-only

Read current output variable values for an OpenMDAO problem and optionally convert them to specified units. Use it to inspect model results by variable name.

Instructions

Read current values of variables, optionally converted to given units.

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

Input Schema

NameRequiredDescriptionDefault
namesYesPromoted names of outputs to return.
unitsNoUnits per variable name, e.g. {'mass': 'kg'}.
problem_idYes
allow_missingNo

Output Schema

NameRequiredDescriptionDefault
errorNo
valuesNo
missingNo

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?

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds that values are 'current' and that unit conversion is optional, but says nothing about the allow_missing fallback, error behavior for unknown names, or pagination/size limits on the names array.

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. It is appropriately short for a simple read tool, though it could spend one more clause on the missing-name behavior.

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 basic read-plus-conversion contract is clear. Gaps remain around the undocumented allow_missing flag and what happens when requested names are not promoted outputs.

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 50%, and the description adds the meaning of the optional unit conversion beyond what the schema states. However, the allow_missing parameter has no description in schema or description, leaving its behavior (skip vs error on unknown names) undisclosed.

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 ('Read') and resource ('current values of variables') plus an optional transformation (unit conversion). This separates it from siblings like list_variables and get_problem_spec, though it never names them explicitly.

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?

The description gives no when-to-use or when-not-to-use guidance and does not point to any alternative such as list_variables or get_problem_spec. The read semantics are implied by the verb only.

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