commune-mcp

Official

by commune-dev

Overview Schema Source Related Servers Discussions(1)Admin

Python

Remote

get_thread_metadata

Retrieve triage metadata including tags, status, and assignment for a thread using its ID.

Instructions

Get triage metadata for a thread: tags, status, and assignment.

Args: thread_id: The thread ID

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": "get_thread_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It indicates a read operation ('Get') and enumerates the returned fields, which is some transparency. However, it does not disclose error handling, permissions, or response behavior beyond those fields.

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 concise: a single sentence stating the purpose followed by a minimal args block. Every part is relevant and front-loaded, with no unnecessary fluff.

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?

For a single-parameter getter, the description is functional but sparse. It does not guide the agent on when to use this tool alongside many thread-related siblings, and the parameter documentation is unhelpful. The output schema may cover return values, but the description still lacks usage direction.

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

Parameters1/5

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

The only parameter thread_id is described as 'The thread ID,' which merely restates the parameter name and schema title. It provides no additional meaning about format, source, or constraints, and schema coverage is 0%.

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 clearly states a specific verb ('Get'), resource ('thread'), and scope ('triage metadata: tags, status, and assignment'). This distinguishes it from sibling tools like get_thread_messages (messages), list_threads (listing), and mutation tools like tag_thread.

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?

No explicit guidance is provided on when to use this tool versus alternatives. It does not mention exclusions or recommend sibling tools for different use cases, leaving the agent to infer based on the name and description alone.

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