Skip to main content
Glama

close_conversation

Close a completed conversation to free its resident slot and discard its history and job results. If it is still running, cancel and confirm termination first.

Instructions

完了した会話を閉じる。native会話は子プロセスの終了を待って常駐枠を返し、履歴とジョブ結果を破棄する。実行中は取消と終了確認が先に必要

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "close_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that history and job results are discarded (irreversible data loss), that a resident slot is released, and that native conversations block on child-process exit. It does not say what happens to non-native conversations or what the call returns.

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 compact sentences with the destructive outcome and precondition front-loaded; nothing is padding. The term 'native会話' is used without definition, which costs a little clarity but not length.

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 one-parameter destructive tool with no annotations and no output schema, the description covers consequences, blocking behavior, and preconditions well. It falls short only on return/result signaling and on how non-native conversations differ.

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 coverage is 0% and the description never mentions conversation_id, so it adds no meaning beyond the schema. The single parameter is nonetheless self-explanatory by name plus UUID format/pattern, so the gap is small rather than fatal.

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?

States a specific verb+resource (close a completed conversation) and adds scope detail about native conversations waiting for child-process exit. It never names a sibling for contrast, though the note that cancellation must come first implicitly separates it from cancel-style tools.

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?

Gives a concrete precondition: a running conversation must first be cancelled and its termination confirmed. What is missing is any positive routing guidance, i.e. when to prefer this over leaving a conversation open or over cancel_agent.

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