Skip to main content
Glama

Configure approx totals

configure_approx_totals
Idempotent

Configure finite-difference or complex-step approximation of model total derivatives, including form, step, and step calculation, or remove it by passing a null spec.

Instructions

Approximate the model's total derivatives by finite differences (forward/central/backward, step, step_calc) or complex step; pass spec=null to remove the approximation.

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

Input Schema

NameRequiredDescriptionDefault
specNo
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.7/5.0
Behavior3/5

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

Annotations only declare idempotentHint, so the description carries the rest of the behavioral load. It usefully discloses that spec=null removes the approximation, which is a mutate-to-remove semantic, but does not say whether the setting persists on the problem or what happens to existing settings when a partial spec is supplied.

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 removal semantics are placed at the end where they are easy to catch. Dense parenthetical listing of options is acceptable but slightly squeezes the readability.

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

Completeness5/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 described, and the tool has only two parameters with one required. The description covers the action, options, and removal path, which is sufficient for an agent to invoke it correctly.

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

Parameters4/5

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

Schema coverage is reported as 0% and the spec fields sit inside a $defs object, so the description earns credit for naming the meaningful knobs (form, step, step_calc, complex step) and, more importantly, for explaining the null case of spec, which the schema only encodes structurally.

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: approximating the model's total derivatives, with the approximation schemes named. It is clear this configures approximation rather than computing totals, though it never names the compute_totals sibling to sharpen the distinction.

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 implied by the content (use this to enable or remove an approximation scheme), and the removal path via spec=null is stated explicitly. There is no explicit when-to-use/when-not guidance or reference to alternatives such as compute_totals.

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