nc-mcp-server

get_thread

Read-onlyIdempotent

Retrieve a summary of a specific Talk conversation thread by providing its token and thread ID, returning key details like title, reply count, and last activity.

Instructions

Get details of one thread in a Talk conversation.

Returns the thread's summary, not its messages; use get_messages(token, thread_id=...) to read the messages.

Args: token: The conversation token. Use list_conversations to find tokens. thread_id: The thread ID, which is the ID of the thread's first message. Shown as "[thread ]" in get_messages output.

Returns: JSON object with thread_id, token, title, num_replies, last_activity, notification_level and first/last messages as compact lines.

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": {
      "token": "<token>",
      "thread_id": "<thread_id>"
    },
    "name": "get_thread"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes
`thread_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.0Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral context by clarifying that this returns a summary (not messages) and lists the exact fields returned, including 'compact lines' for first/last messages. No contradictions with 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?

The description is well-structured with clear sections for purpose, arguments, and returns. Every sentence serves a purpose, and the key scoping statement is front-loaded. It is slightly longer than strictly necessary but avoids redundancy.

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

Completeness5/5

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

For a simple read-only tool with two required parameters, the description is complete. It explains how to discover both parameters, what the tool does and does not return, and the returned fields. The presence of an output schema further reduces the need to detail return formats, but the description already covers them thoroughly.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters in practical terms. It tells the user that token is a conversation token found via list_conversations, and that thread_id is the ID of the thread's first message, as shown in get_messages output. This adds real meaning 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 opens with a specific verb and resource: 'Get details of one thread in a Talk conversation.' It immediately clarifies the tool's scope and differentiates itself from get_messages by explicitly stating it returns the summary, not messages. This makes the purpose unmistakable and distinct from close siblings.

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?

The description gives explicit guidance for a key alternative: 'use get_messages(token, thread_id=...) to read the messages.' It also tells the user how to obtain the token via list_conversations. However, it does not contrast with other thread-related siblings like list_threads or get_conversation, so some when-to-use context is missing.

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

Deploy Server