Skip to main content
Glama

manage_thread

Destructive

Archive or unarchive an exact item or Support conversation for your account, for free. Support cannot be blocked or reported. Item Block closes live offers only.

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": {
      "action": "<action>",
      "conversation_id": "<conversation_id>",
      "request_id": "<request_id>"
    },
    "name": "manage_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
reasonNo
max_feeNo
request_idYes
conversation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description does add non-obvious context beyond them: the operation is free, Support targets cannot be blocked/reported, and item blocks only close live offers. It does not disclose what is destroyed by archiving, whether actions are reversible, or what the reason/max_fee inputs affect, which matters for a destructive mutation.

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

Conciseness3/5

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

Three short sentences with no filler, and the main capability is front-loaded. But the trailing constraints are telegraphic and hard to parse ("Item Block closes live offers only"), and "for free" is an unanchored phrase that reads as noise without context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, open-world mutation tool with five parameters, three of them required, zero schema documentation, no output schema, and a five-value action enum. Given that complexity, the description is far too thin: it omits per-action semantics, required inputs, and consequences, leaving the agent unable to call it correctly on report/block/unblock.

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% across five parameters, so the description must carry the burden, and it does not. It never explains the action enum's five members, the purpose of reason (required min 8 / max 2000 chars for some actions), max_fee, or the request_id idempotency token. Only a loose mapping of 'exact item or Support conversation' to the target exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening names a concrete verb pair and resources ("Archive or unarchive an exact item or Support conversation"), so the primary action is identifiable. However, the schema's action enum contains five values (archive, unarchive, report, block, unblock) and the description only defines the first two directly; report/block/unblock are addressed obliquely ("Support cannot be blocked or reported", "Item Block closes live offers only"). The tool's overall purpose as a mixed-action management endpoint is only partially conveyed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is one exclusionary hint — Support cannot be blocked or reported — which tells the agent a case not to use two of the actions. Beyond that, there is no guidance on when to choose this tool over siblings such as reply, respond, or list_inbox, no prerequisites, and no explanation of when to pick one action over another. Usage is left to be inferred from the enum.

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