Skip to main content
Glama
Sign In
threadmap-mcp

threadmap-mcp

by Advertflair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

threadmap_fork

Create a clean conversation branch from any message index to explore alternative paths without losing original context. Preserve original intent by forking at the exact point needed.

Instructions

Fork the conversation from a specific message index. Creates a clean branch with only context up to that point.

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": {
      "sessionId": "<sessionId>",
      "messageIndex": "<messageIndex>",
      "branchName": "<branchName>"
    },
    "name": "threadmap_fork"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes
branchNameYesName for this branch (e.g. 'auth-restart')
messageIndexYesIndex of message to fork from (0-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It reveals the key behavior of creating a clean branch with only context up to the fork point, which is important. However, it does not disclose side effects like whether the original thread is modified, persistence, or permissions.

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?

Two sentences, front-loaded with the action, and every word adds meaning. No filler or redundancy.

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

Completeness4/5

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

Given the tool's simplicity, the description covers the core purpose and outcome. It does not mention return values or edge cases, but for a forking operation the description is sufficiently complete for an agent to understand when and how to invoke it.

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?

Schema coverage is 67%: messageIndex and branchName have descriptions, but sessionId does not. The description adds minimal semantic value beyond the schema, mainly restating the fork point concept. It does not clarify sessionId's purpose or format.

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 action ('Fork the conversation') and the resource ('from a specific message index'), and distinguishes it from siblings by specifying it creates a new branch with limited context. This is a precise verb+resource combination.

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 on when to use this tool versus alternatives like threadmap_branch_context or threadmap_reset. The description implies usage for branching, but does not state conditions or exclusions.

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

Deploy Server

Other Tools