Skip to main content
Glama

Close or reopen a conversation

thread_close
DestructiveIdempotent

Closes (or, with reopen:true, reopens) one of your conversations. A new message from you reopens a closed conversation. Without confirm:true it only previews. Locked conversations cannot be changed.

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": {
      "thread": "<thread>"
    },
    "name": "thread_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
reopenNo
threadYesConversation reference (TH-…) from threads_list.
confirmNofalse = preview only, nothing is sent. true = really send/apply after the human agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description goes beyond them by explaining the preview-by-default safeguard, that reopening is possible through a new message or reopen:true, and that locked conversations are immutable. That materially reduces the apparent risk of a destructive write. It does not describe what the preview response contains.

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?

Three short sentences, front-loaded with the action and parenthetical for the inverse mode; no filler. Slight cost in that the reopen aside interrupts the main clause.

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 destructive mutation with no output schema, the description covers the safety path, the reversibility story, and the precondition. The only gap is what a successful or preview response looks like, which the agent must infer.

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 67% and the undocumented parameter is reopen, whose semantics the description spells out ('with reopen:true, reopens'). It also reinforces confirm's meaning as preview versus apply, adding behavioral meaning beyond the schema text.

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 ('Closes ... one of your conversations') and explicitly covers the inverse operation via the reopen flag. It does not differentiate from nearby siblings such as thread_set_flags, but the operation itself is unambiguous.

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 states the operating condition (needs confirm:true to actually apply, otherwise preview) and a hard constraint ('Locked conversations cannot be changed'). It stops short of naming an alternative tool for cases where closing is not the right call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources