Skip to main content
Glama

Compute totals

compute_totals

Computes total derivatives of selected OpenMDAO outputs with respect to chosen inputs at the current point, running the model first when needed.

Instructions

Total derivatives of 'of' with respect to 'wrt' at the current point (runs the model first).

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>",
      "of": "<of>",
      "wrt": "<wrt>"
    },
    "name": "compute_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
ofYes
wrtYes
problem_idYes
return_formatNoby_pair

Output Schema

NameRequiredDescriptionDefault
errorNo
jacobianNo
messagesNo
captured_outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With only a title annotation, the description still discloses the key behavioral trait: it executes the model before differentiating, which implies compute cost and side effects on model state. It says nothing about failures, cost expectations, or whether the model run mutates anything, leaving real behavioral gaps.

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?

One sentence plus a high-value parenthetical; nothing is redundant and the computation is front-loaded. The jargon 'totals' is only clarified by the expansion to 'total derivatives'.

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 no explanation, but for a 4-parameter tool with zero schema coverage and no annotations, the description omits what problem_id refers to and how the 'of'/'wrt' name arrays should be formed. The notion of a 'current point' is also unexplained relative to the problem-loading siblings.

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 0%, so the description carries the full burden, yet it only names 'of' and 'wrt' without explaining that they are arrays of qualified names, and says nothing about problem_id or the return_format enum (by_pair vs dense). Only half the parameters receive even nominal mention.

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 mathematical operation ('total derivatives of X with respect to Y') rather than restating the name, and the parenthetical clarifies that the model is executed first. It does not explicitly position itself against siblings such as check_totals_sweep or configure_approx_totals, so an agent must infer the difference.

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?

'At the current point' implies usage context (derivatives evaluated at the already-set input values) and 'runs the model first' hints at cost, but there is no explicit when-to-use/when-not guidance nor any named alternative for verification-style workflows.

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