commune-mcp

Official

by commune-dev

Overview Schema Source Related Servers Discussions(1)Admin

Python

Remote

set_thread_status

Update a thread's triage status to open, needs_reply, waiting, or closed to manage email responses.

Instructions

Set the status of a thread for triage.

Valid statuses: "open", "needs_reply", "waiting", "closed"

Args: thread_id: The thread ID status: New status — one of: open, needs_reply, waiting, closed

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

Input Schema

Name	Required	Description	Default
`thread_id`	Yes
`status`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 28, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states valid statuses but does not mention side effects, reversibility, permissions, or what happens on invalid input. As a mutation tool, this lack of behavior context is a notable gap.

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 description is short and front-loaded with the core action. However, the list of valid statuses is repeated twice (in the intro and in the Args section), which is slightly redundant but not overly verbose.

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

Completeness3/5

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

The tool is simple with only two parameters and an output schema exists, so return values need not be described. The description covers the essentials for making a call, but lacks context about side effects, edge cases, or how this relates to other thread triage operations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by explaining both parameters: thread_id is 'The thread ID' and status is 'New status — one of: open, needs_reply, waiting, closed' with the allowed values repeating in the prose. This adds meaning well beyond the bare schema.

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 uses a specific verb and resource: 'Set the status of a thread for triage.' It clearly distinguishes this from siblings like assign_thread, tag_thread, and untag_thread by focusing on the status field specifically.

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 phrase 'for triage' implies the tool is meant for updating triage status, but the description does not explicitly compare it to alternatives or state when not to use it. Usage is implied rather than fully spelled out.

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