Skip to main content
Glama

merge_topic

Merge one Worktrail topic into another by moving all its threads, uniting repositories, keeping the destination summary, and deleting the source topic.

Instructions

Merge one topic into another, FOR THE ENGINEER: every thread under topic moves to into (its assignment time kept), repositories are united, into keeps its own summary and conclusion, and topic is deleted. Thread records are untouched. Both are existing topic names, exactly. Requires engineer_asked=true, which you may pass only when the engineer asked to merge or tidy topics — never on your own judgment; say which goes into which before calling.

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": {
      "topic": "<topic>",
      "into": "<into>"
    },
    "name": "merge_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
intoYes
topicYes
engineer_askedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does well on data effects: threads move with assignment time preserved, repositories are united, `into` keeps its summary and conclusion, `topic` is deleted, thread records untouched. It does not state irreversibility or whether the merge can be undone, and permissions are only implied via the engineer_asked gate. Return values are covered by the output schema, so that omission is acceptable.

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?

Front-loaded with the core action, then the effect list, then the gating rule — a sensible order. Every clause carries information, though the long parenthetical effect chain and the "FOR THE ENGINEER:" fragment make it denser than it needs to be.

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 destructive merge operation with no annotations and an output schema present, the description covers source/target semantics, migration of threads, repository union, survival of `into`'s summary, deletion of `topic`, and the authorization gate. An agent has everything needed to decide and invoke 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, and it does: `topic` is identified as the source that gets deleted, `into` as the surviving target, and both must be existing topic names matched exactly. `engineer_asked` is explained as a permission gate with explicit conditions for when it may be set to true — meaning the schema alone would never convey.

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 verb and resource ("Merge one topic into another") and immediately defines the directionality: every thread under `topic` moves to `into`, and `topic` is deleted. This makes it unmistakably distinct from siblings like assign_topic or list_topics without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition (engineer_asked=true, only when the engineer asked to merge or tidy topics, "never on your own judgment") and a procedural instruction to state which topic goes into which before calling. The when-not guidance is unusually strong; no sibling alternative is named, but the gating condition is unambiguous.

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