Skip to main content
Glama

Configure solvers

configure_solvers
Idempotent

Set a group's nonlinear and linear solvers by dotted path (empty for root) to configure coupled-loop methods like NonlinearBlockGS or Newton with DirectSolver; both slots are overwritten.

Instructions

Set the nonlinear and linear solvers of one group (dotted path, empty for the root), e.g. NonlinearBlockGS or Newton with DirectSolver for a coupled loop. Both slots are overwritten.

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_solvers"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
problem_idYes
linear_solverNo
nonlinear_solverNo

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 supply only idempotentHint=true; the one genuinely valuable behavioral disclosure is 'Both slots are overwritten,' which warns that prior solver config is replaced. However, it is ambiguous whether supplying only one slot clears the other (both schema slots default to null), and nothing is said about errors for an unknown group path or about re-applying to an already-configured group.

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?

Two tight sentences with zero padding, and the scope constraint (group path, empty = root) plus the overwrite warning are front-loaded before the illustrative example.

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 needn't be explained, and idempotency is declared. Still, for a mutation tool that replaces configuration, the description should resolve the one-slot-vs-both ambiguity and state failure behavior for invalid group paths.

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% at the top level, so the description must compensate. It clarifies 'group' (dotted path, empty for root) and hints at the coupling between the two solver slots, but adds nothing about problem_id or about which spec fields (atol/rtol/maxiter/linesearch) interact with the overwrite semantics - those are only covered by the nested $defs.

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+resource: set the nonlinear and linear solvers for one group, with concrete solver examples (NonlinearBlockGS, Newton + DirectSolver). The resource is distinct from sibling configure_* tools, though the description never names those siblings to sharpen the boundary.

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?

Implies usage ('for a coupled loop') but gives no explicit when-to-use/when-not guidance and no prerequisites, e.g. whether the problem must be loaded first or whether this belongs before run_model. The agent must infer placement in the workflow.

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