Skip to main content
Glama

Close Binary

close_binary
Destructive

Drain pending provider requests, optionally write an atomic analysis snapshot, and close the active target with all provider resources; subsequent requests wait until shutdown finishes.

Instructions

Drain earlier provider requests, optionally write a provider-neutral analysis snapshot atomically to the caller-supplied path, then close the active target and every provider resource started for it. Later provider requests wait until this lifecycle operation finishes. Existing files require explicit overwrite; a failed save leaves the session open so cached analysis is not lost. Metadata edits prevent immutable snapshot saves until the session is recreated; export_evidence_bundle preserves mutable observations before closing without a snapshot.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
overwriteNoWhether an existing destination may be replaced.
snapshot_pathNoAbsolute local filesystem path for the analysis snapshot; relative paths are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive, non-idempotent, non-read-only behavior, and the description adds substantial context on top: provider requests are drained first, concurrent requests block until the lifecycle finishes, the snapshot write is atomic, a failed save leaves the session open so cached analysis survives, and metadata edits make immutable snapshot saves impossible. These are the exact failure and ordering semantics an agent needs before invoking a destructive teardown.

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?

The description is front-loaded with the action sequence, which is appropriate for a multi-step lifecycle operation, and nearly every clause carries meaning. Some sentences are dense and pack two independent ideas, but none are filler.

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 destructive lifecycle tool with no output schema, the description covers ordering, atomicity, failure behavior, concurrency, and the alternative export path, which is nearly everything an agent needs. It stops short of describing what the caller observes on success or how cancellation or timeout behaves, which would complete the picture.

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 100%, so the baseline is 3, but the description earns above that by explaining that the snapshot is optional and that an existing destination requires explicit overwrite — semantics the schema mentions only as a default value. It does not add anything about why an absolute path is required beyond what the schema already states.

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 names a specific verb and resource and decomposes the operation into its three phases: draining outstanding provider requests, optionally writing an analysis snapshot, and closing the target plus all provider resources. It also distinguishes this teardown operation from export_evidence_bundle, so an agent can tell the two apart without opening a schema.

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?

Conditions are stated clearly: overwrite must be explicit for an existing destination, and when metadata edits have occurred the agent cannot save an immutable snapshot and should use export_evidence_bundle instead. What is missing is an explicit positive trigger phrase such as 'call this when the analysis session is finished', but the implicit guidance is strong and the alternative is named.

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