Skip to main content
Glama

close

Archive a topic's Codex and Antigravity conversations without deleting them, letting open incidents remain tracked and new messages reopen the topic in a fresh conversation.

Instructions

Close a topic (host only): its Codex and Antigravity conversations are archived (never deleted) once their turn is over and the user is out of the app; its open incidents leave status (track keeps them). A new send on this topic reopens it in a fresh conversation. Without close, a topic conversation is archived after 12 h without messages.

Args: topic: the topic to close.

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

Input Schema

NameRequiredDescriptionDefault
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.7
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "closeOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description supplies the substantive behavior: data is archived, never deleted, incidents are released from status but retained by track, and a subsequent send reopens the topic in a fresh conversation. That is exactly the 'what actually happens / what gets affected' context that annotations cannot express, and it is consistent with destructiveHint=false.

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 core behavior and the 12-hour default are front-loaded in the first two sentences, and every clause carries real information. The trailing 'Args:' block is wasted space since it repeats the parameter name without adding meaning.

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 single-parameter mutation with no output schema, the description covers consequences, eligibility, and the default it overrides thoroughly. The remaining gap is the topic identifier's expected form and any error/not-found behavior, which an agent would need to call it reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 parameter, so the description must compensate — but 'topic: the topic to close' is a tautological restatement of the parameter name with no format, identifier type, or validation guidance. An agent still cannot tell whether to pass a name, slug, or ID.

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?

States a specific verb and resource ('Close a topic') and immediately qualifies scope with '(host only)', which distinguishes it from siblings like cancel, release, or send. The consequences spelled out (archiving, incident status, reopen behavior) leave no ambiguity about what the operation does.

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?

The description gives a clear rationale for invoking it by contrasting with the default: 'Without close, a topic conversation is archived after 12 h without messages,' so the agent knows close means immediate archiving. It also restricts eligibility ('host only') and notes the preconditions (turn over, user out of the app). It does not name any alternative sibling tool or an explicit when-not-to-use case, so it stops 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.