Skip to main content
Glama

Coline

Follow thread

follow_thread
Idempotent

Follows a thread (the person hears about new replies) or stops following 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": {
      "workspace": "<workspace>",
      "type": "<type>",
      "conversationId": "<conversationId>",
      "rootMessageId": "<rootMessageId>",
      "following": "<following>"
    },
    "name": "follow_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
followingYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
rootMessageIdYes
conversationIdYesChannel or direct message id, from list_conversations.

Output Schema

NameRequiredDescriptionDefault
followingYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, non-destructive, idempotent mutation. The description adds useful behavioral context by explaining that following causes the person to hear about new replies. It does not cover permissions, error behavior, or other side effects, so it adds only moderate value beyond the annotations.

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?

The description is a single concise sentence with no wasted wording. The action and its effect are front-loaded and immediately understandable. It is appropriately sized for the stated purpose.

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?

The tool requires five parameters, yet the description addresses only the follow/unfollow concept and does not explain how to identify the thread or what type means. Although annotations and an output schema reduce some burden, the definition remains incomplete for an agent to invoke it confidently. More parameter context is needed.

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 only 40%, so the description should compensate for undocumented parameters. It explains the meaning of following and the notification effect, but it does not clarify type, rootMessageId, or how the thread is identified. With five required parameters, this leaves significant semantic gaps.

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 states a specific verb and resource: follow or stop following a thread. It clearly distinguishes the two modes of the operation. It does not explicitly differentiate itself from sibling tools such as read_mail_thread or organize_mail_thread, so it falls short of a 5.

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 description implies when to use the tool by explaining that following means the person hears about new replies and that it can also stop following. However, it gives no explicit when-to-use guidance, exclusions, or alternative tools. The usage is mostly self-evident from the toggle nature of the operation.

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