Skip to main content
Glama

Query cases

query_cases
Read-only

Query OpenMDAO case recordings with CaseReader to list cases, retrieve history, find best feasible designs, inspect active constraints, or rank sensitivities.

Instructions

Query a case recording with CaseReader: list, history, best_feasible, active_constraints, or sensitivity_ranking. Defaults to the problem's latest recording.

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>",
      "query": "<query>"
    },
    "name": "query_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
max_casesNo
active_tolNo
problem_idYes
recorder_pathNo
feasibility_tolNo

Output Schema

NameRequiredDescriptionDefault
bestNo
errorNo
queryNo
historyNo
n_casesNo
messagesNo
recorder_pathNo
sensitivitiesNo
active_constraintsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add context; it does so by disclosing the CaseReader backing store and the default-to-latest-recording behavior. It omits what happens when no recording exists (error vs empty result) and any behavior of the tolerance parameters.

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 short sentences, front-loaded with the verb and resource, then the mode list and default. No filler or repetition of the title.

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 not be described, and the read-only nature is covered by annotations. Still, for a six-parameter tool with zero schema descriptions, the unspecified tolerance and limit parameters leave an agent guessing at call 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 0% across six parameters, so the description must carry the load. It explains the `query` modes and implicitly the `recorder_path` default, but says nothing about max_cases, active_tol, or feasibility_tol, leaving half the surface undocumented anywhere.

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?

Names a specific verb (query) and resource (case recording via CaseReader) and enumerates the five query modes, which lets an agent distinguish this from siblings like get_outputs or list_variables. It stops short of explicitly contrasting with any named sibling, so it falls just under the top mark.

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 clause 'Defaults to the problem's latest recording' gives useful context about what happens if no recording is chosen, implying the tool reads existing recorded data. However, there is no explicit guidance on when to pick this over get_outputs or list_variables, nor on prerequisites such as whether a recording must already exist.

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