Skip to main content
Glama

close

Destructive

Destroys both session VMs and retains exported local evidence to clean up resources after verification.

Instructions

Destroy both session VMs and retain exported local evidence. Always close when finished.

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": {
      "session": "<session>"
    },
    "name": "close"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the important specifics of exactly what is destroyed (both session VMs) and what survives (exported local evidence). It still omits irreversibility, permission requirements, and behavior on an unknown or already-closed session.

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?

Two short sentences, front-loaded with the destructive effect and followed by the usage rule; no filler. It is arguably too terse given the destructive nature, but nothing written is wasted.

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?

For a destructive, single-parameter tool with no output schema, the definition covers the core effect and the retained artifact, but leaves out irreversibility, failure behavior, and any ordering relationship with the export sibling. An agent could invoke it correctly but without full awareness of consequences.

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% for the single required 'session' parameter, so the description carries some burden; it ties the call to a session context implicitly through 'session VMs' but never states the identifier form or expected value. For a single, largely self-evident parameter this is a minimal but tolerable 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 concrete verb and object ('Destroy both session VMs') plus a retention side effect ('retain exported local evidence'), which resolves the ambiguity of the generic name 'close'. It does not explicitly name a contrasting sibling (e.g., export or start), so it stops short of full sibling differentiation.

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?

'Always close when finished' gives a clear timing cue for when to invoke, but there is no guidance on when not to close, no prerequisite ordering (e.g., export evidence first, despite an 'export' sibling existing), and no mention of what happens if the session is already closed.

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