Skip to main content
Glama

threads_get_agent_status

Read-onlyIdempotent

Says whether the AI agent is on hold in one conversation: paused, who paused it ("operator" for a person's Pause / take-over; null for a pause a manual reply set) and since when (UTC).

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>"
    },
    "name": "threads_get_agent_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds genuinely new behavioral detail: the meaning of the 'operator' value versus a null pauser, and that the timestamp is UTC — return semantics an agent cannot get from the schema or annotations.

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?

A single front-loaded sentence with no filler; every clause carries information. The nested parenthetical for the 'operator'/null distinction is slightly dense to parse but is the most economical way to express it.

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?

With no output schema, the description must carry return semantics, and it does for pause state, pauser identity and pause time. What the response looks like when the agent is not paused, and the actual field names, remain unstated — a modest gap for a two-parameter read tool.

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%, with thread_id and in_workspace both documented in the schema itself, so the baseline is 3. The phrase 'one conversation' reinforces that thread_id targets a single thread but adds no syntax or format guidance beyond what the schema already provides.

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 act on a specific resource: reports whether the AI agent is on hold in one conversation, plus who paused it and since when. The scope ('one conversation', i.e. single-thread) is clear enough to distinguish it from bulk status tools, though it never names its write-side counterpart threads_set_agent_paused.

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?

The read-only nature and the returned fields imply the use case (checking before replying or before calling the pause setter), but there is no explicit when-to-use or when-not-to-use statement and no named alternative. An agent must infer the routing from field names alone.

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.