nc-mcp-server

set_thread_notification_level

Idempotent

Set your notification level for a thread (default, always, mention, never). Choosing anything but 'never' subscribes you; 'never' unsubscribes.

Instructions

Set the current user's notification level for a thread.

Setting any level other than "never" also makes the user follow the thread, so it shows up in list_subscribed_threads; "never" removes it from that list.

Args: token: The conversation token. Use list_conversations to find tokens. thread_id: The thread ID (the ID of the thread's first message). level: One of "default" (use the conversation's setting), "always" (every message), "mention" (only when mentioned) or "never".

Returns: JSON object of the updated thread (same shape as get_thread).

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

Input Schema

Name	Required	Description	Default
`level`	Yes
`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.6/5.0

Behavior4/5

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

Annotations indicate mutation (readOnlyHint=false) and idempotency (idempotentHint=true). The description adds important behavioral context: the side effect of following/unfollowing the thread based on the level, and the return value shape. It does not cover error conditions or permissions, but the annotations already establish safety profile.

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?

Well-structured with a clear purpose sentence, a note on side effects, a compact Args list, and a Returns line. Every sentence adds value, and the most important information is front-loaded.

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 3-parameter tool with an output schema, the description covers all needed details: token acquisition, thread_id semantics, level options, and return shape. The side effect is disclosed. An agent has everything required to invoke it correctly.

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 coverage is 0%, so the description must compensate. It fully explains each parameter: token ('Use list_conversations to find tokens'), thread_id ('the ID of the thread's first message'), and level (enumerates all four values with meanings). This is far beyond what the schema provides.

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?

States a specific action ('Set the current user's notification level for a thread') with a clear verb and resource. It also explains a key side effect (following/unfollowing) that distinguishes it from other thread-related tools. The purpose is unambiguous and distinct from siblings like rename_thread or list_threads.

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?

Provides explicit guidance on how to find the token ('Use list_conversations to find tokens'), explains the level options with their effects, and notes the side effect on subscription. It does not explicitly state 'use this instead of X' but the tool's unique role is clear from the description.

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

Deploy Server