Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Close Database

close_database

Releases an IDA database worker by saving and shutting it down when the last user detaches; force shutdown with terminate=true. Other instances remain unaffected.

Instructions

Release an IDA database worker: saved and shut down when the last user detaches; terminate=true forces shutdown. Use when its analysis is finished or no longer needed — the other instances are unaffected.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "close_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoSave the database before closing
terminateNoForce shutdown even while other agents still hold leases on this worker
instance_idNoREQUIRED whenever more than one database is open (from open_database's result or list_databases()); optional only while exactly one instance is live.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / instance_id / description
      Previous value: -"Instance id; defaults to the current target"New value: +"REQUIRED whenever more than one database is open (from open_database's result or list_databases()); optional only while exactly one instance is live."
    • changedInput schema / properties / terminate / description
      Previous value: -"Also close GUI instances; headless workers are always shut down (saved first) when their last user detaches"New value: +"Force shutdown even while other agents still hold leases on this worker"
  2. First observedv0.9.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses meaningful behavior: deferred shutdown on last detach, forced termination override, and lack of impact on other instances. It does not describe return values or whether unsaved changes are handled when save=false, but the lifecycle semantics are well covered.

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?

The description is two compact sentences, front-loaded with the core operation and followed by usage and safety context. No sentence is wasted.

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?

For a three-parameter lifecycle tool with fully documented schema and no output schema, the description covers purpose, timing, and key safety behavior sufficiently. Minor gaps remain around return values and unsaved-change behavior when save=false, but those are not critical for correct invocation.

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 100%, so all three parameters are already documented in the schema. The description reinforces terminate=true behavior but adds little beyond that, which is appropriate given the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource combination ('Release an IDA database worker') and explains the core lifecycle behavior: saved and shut down on last detach, or forced shutdown with terminate=true. It is clearly distinguishable from siblings like save_database and open_database.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when to use the tool: 'when its analysis is finished or no longer needed.' It also notes that other instances are unaffected, helping avoid misuse. No explicit alternative tool is named, so it falls short of a 5.

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

Deploy Server

Other Tools