Skip to main content
Glama
Sign In
threadmap-mcp

threadmap-mcp

by Advertflair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

threadmap_branch_context

Get a summarized context packet for a branch, including intent and messages up to the fork point, to understand conversation history.

Instructions

Get the context packet for a specific branch — summarized intent and messages up to the fork 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>",
      "branchId": "<branchId>"
    },
    "name": "threadmap_branch_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchIdYesBranch ID returned from threadmap_fork
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool returns a context packet containing summarized intent and messages up to the fork point, implying a read-only operation. No contradictions found.

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 a single, front-loaded sentence with no filler. Every word adds value.

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?

Even without an output schema, the description explains what the context packet includes ('summarized intent and messages up to the fork point'). For a simple 2-parameter read tool, this is sufficient, though sessionId remains ambiguous.

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

Parameters2/5

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

Schema coverage is only 50%: branchId is documented but sessionId is not. The description only says 'specific branch' and provides no additional meaning for sessionId. It fails to compensate for the undocumented parameter.

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 uses a specific verb 'Get' and resource 'context packet for a specific branch', clearly distinguishing it from sibling tools like threadmap_fork or threadmap_status. It precisely states what the tool does.

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 clearly implies when to use this tool: when you need a branch's summarized intent and messages up to the fork point. It doesn't explicitly mention alternatives or when not to use, but the context is unambiguous.

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