time-messenger-mcp-server

get_thread

Retrieve a specific thread's information by providing the team ID and thread ID.

Instructions

Get information about a specific 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": {
      "team_id": "<team_id>",
      "thread_id": "<thread_id>"
    },
    "name": "get_thread"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	Yes	Team ID
`thread_id`	Yes	Thread ID (root post ID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 1, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get information' implies a read operation but does not clarify whether it returns metadata, messages, stats, or other data, nor does it disclose side effects, permissions, or return format. This is minimal disclosure beyond the operation's name.

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 a single, concise sentence with no unnecessary words. While it is short, it is not bloated and effectively communicates the basic operation, though it sacrifices specificity.

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?

For a simple 2-parameter tool with no output schema and no annotations, the description should clarify that it returns thread metadata, not messages or stats, and distinguish it from siblings. The current description is too generic for an agent to reliably select and invoke the tool correctly.

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

Parameters3/5

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

The input schema already provides full coverage with descriptions for both parameters, including 'Thread ID (root post ID)'. The tool description adds no additional meaning or context for the parameters, so it earns the baseline score for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a 'get' operation on a 'thread', but 'information' is vague and does not specify what aspects of the thread are returned. It does not differentiate from sibling tools like get_thread_messages or get_thread_stats, so the purpose is not precisely scoped.

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 guidance is given on when to use this tool versus alternatives. It does not mention any exclusions, contexts, or related tools, leaving the agent to infer usage from the name alone.

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