Skip to main content
Glama

close_conversation

End a shared chat as lead or co-lead, expiring all tokens and unused invitations. Use it to close a discussion and revoke participant access.

Instructions

Close the discussion as lead or co-lead. All tokens and unused invitations expire.

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

Input Schema

NameRequiredDescriptionDefault
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the key side effect: 'All tokens and unused invitations expire.' It also states the permission prerequisite. It stops short of saying whether the action is reversible or what happens to existing messages, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and the actor, followed by the consequence. Nothing is redundant and no sentence fails to earn its place.

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, no-annotation, no-output-schema tool, the description covers the action, the permitted caller and the destructive side effect, which is enough to invoke it correctly. The remaining gaps are reversibility and the meaning of the token parameter.

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 coverage is 0%, so the lone required parameter 'token' has no documented meaning anywhere; the description never mentions it or clarifies whether it identifies the conversation or is an access credential. The description therefore fails to compensate for the coverage gap on a mandatory parameter.

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 names a specific verb and resource ('Close the discussion') and adds the authorization scope ('as lead or co-lead'), which clearly separates it from siblings like create_conversation, join_conversation and post_message. It loses a point only because it says 'discussion' where the tool and siblings say 'conversation', a minor naming drift.

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?

Usage is implied rather than stated: closing is clearly a terminal action, and the caller prerequisite (lead or co-lead) is given. There is no explicit when-to-use, when-not-to-use, or reference to an alternative outcome (e.g. archiving or leaving a conversation), so an agent must infer the timing.

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