Skip to main content
Glama

threads_set_agent_paused

Puts the AI agent on hold in ONE conversation so a person can answer it (paused=true), or hands the conversation back to the agent (paused=false). The same as the Pause / Resume button in the inbox: while paused the agent does not answer that conversation, and no resume policy lifts the pause — only paused=false or the Resume button does. Other conversations and the agent itself keep working. For a person's own client (API key or MCP); an agent cannot call it.

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_id": "<thread_id>",
      "paused": "<paused>"
    },
    "name": "threads_set_agent_paused"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedYestrue: the agent stops answering this conversation. false: it answers again.
thread_idYesThe conversation: its DialogBrain thread id (e.g. "571") or its channel ref (e.g. "telegram:369277159"), as search.threads returns them.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses real behavioral consequences: while paused the agent does not answer that conversation, only paused=false or the Resume button lifts the pause, other conversations and the agent itself keep running, and it is callable only from a person's own client, not by an agent. These are exactly the side effects and authorization constraints an agent needs before invoking a state-changing tool.

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 key action and the paused=true/false split are front-loaded, and the sentences about non-effects (other conversations, the agent itself) and the caller restriction each add distinct value. It is slightly dense with parenthetical asides but not padded.

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 boolean state-setter with three well-documented parameters and no output schema, the description covers scope, side effects, override behavior, and caller eligibility comprehensively. The only omission is any hint of what the call returns or how to confirm the new state.

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 description coverage is 100%, so all three parameters are already documented, establishing a baseline of 3. The description reinforces the single-conversation scope of thread_id and the two-way meaning of paused, but adds no format or syntax detail beyond what the schema provides.

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?

The description states a specific verb and resource (put the AI agent on hold / hand back) and pins the scope to ONE conversation, explicitly contrasting it with the unaffected other conversations. An agent can distinguish this from siblings like agent_silence or agent_handoff without opening any schema.

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 gives clear when-to-use context: pause so a person can answer, resume by setting paused=false, and clarifies the unmistakeable equivalence to the inbox Pause / Resume button, including that no resume policy overrides it. The main gap is that it never names an alternative sibling tool for related operations, leaving routing to inference.

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.