Skip to main content
Glama

Close problem

close_problem
Destructive

Release an OpenMDAO problem from memory and optionally delete its directory and recordings by setting delete_files, freeing resources after model runs.

Instructions

Release a problem from memory; with delete_files, also delete its directory and recordings.

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

Input Schema

NameRequiredDescriptionDefault
problem_idYes
delete_filesNo

Output Schema

NameRequiredDescriptionDefault
errorNo
successNo
files_deletedNo

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?

The annotation destructiveHint=true already warns that this can destroy data, and the description earns credit for specifying exactly what disappears: memory residency by default, plus the directory and recordings when delete_files is set. However, it does not say whether the deletion is irreversible, whether the problem can be reloaded afterwards, or what permissions are needed.

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?

A single semicolon-joined sentence with the default behavior first and the destructive conditional second, with no filler. Every clause contributes information an agent needs to choose the flag safely.

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

Completeness4/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 two-parameter surface is simple. The remaining gap is lifecycle context, such as whether a closed problem can be reloaded or whether delete_files permanently removes files, which matters for a destructive tool.

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 0%, so the description carries the burden, and it does explain the only non-obvious parameter: delete_files also removes the directory and recordings. problem_id's meaning and format are left to the schema pattern, which is a minor gap.

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?

The description gives a specific verb and resource ('Release a problem from memory') plus the conditional effect of the optional flag, so an agent can tell this apart from create_problem/load_problem/update_problem. It stops short of naming a sibling or stating an explicit alternative, so it does not reach the top of the scale.

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 rather than stated: close a problem when it is no longer needed so its memory can be freed, and add delete_files if the on-disk artifacts should go too. There is no explicit when-not-to-use guidance or named alternative for tasks that only want to unload without deleting state.

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