Collide MCP

pending_reconciliations

When a response says two agents' work collides (reconciliations_pending): claim the open collisions, with both sides' intents, changed lines and notes, to merge them. Merge by keeping both sides' work; never by deleting either. After the merge passes the tests, call again with resolve=[id]. Returns the claimed reconciliations and how many stay open.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`repo_id`	No	The repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in.
`resolve`	No	Ids of reconciliations you have merged and verified.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / repo_id / description

Previous value: -"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."New value: +"The repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in."

changedInput schema / required

Previous value: -[
-  "repo_id"
-]New value: +[]

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / repo_id / description

Added value: +"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."

addedInput schema / properties / resolve / description

Added value: +"Ids of reconciliations you have merged and verified."

Changed8 schema fields changedSep 18, 2026

removedInput schema / properties / repo_id / description

Removed value: -"Repository id — the git remote (e.g. github.com/acme/api) or a bare folder name; a #branch suffix scopes to that branch."

removedInput schema / properties / repo_id / title
```
Removed value: -"Repo Id"
```

removedInput schema / properties / resolve / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / resolve / default
```
Removed value: -null
```
addedInput schema / properties / resolve / items
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / resolve / title
```
Removed value: -"Resolve"
```
addedInput schema / properties / resolve / type
```
Added value: +"array"
```

removedInput schema / title

Removed value: -"pending_reconciliationsArguments"

First observedSep 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false, and the description reinforces and sharpens this with an explicit merge rule ('keeping both sides' work; never by deleting either'), which tells the agent exactly what is and isn't allowed. It also discloses the two-phase claim-then-resolve workflow and the return content ('claimed reconciliations and how many stay open'), adding real context beyond the annotations.

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 trigger condition is front-loaded, followed by the merge rule and the resolve step, so an agent can act from the first clause onward. It is a little dense and conversational, but nearly every sentence carries actionable information, so it stays well-structured.

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?

With no output schema, the description compensates by stating what is returned ('the claimed reconciliations and how many stay open') and by covering the full trigger/workflow for both parameters. It is essentially complete for an agent to invoke it correctly, with only minor room to name the non-collision path.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: it explains that resolve carries ids of reconciliations already merged and verified, and that calling with resolve=[id] is a second invocation after tests pass. That workflow-level semantics raises it above baseline.

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

Purpose4/5

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

The description states a specific two-mode behavior: claim open collisions so they can be merged, and later resolve them with resolve=[id]. The verb+resource (claim/merge reconciliations) is clear and concrete. It stops short of explicitly distinguishing itself from the sibling 'claim' tool, so it is strong but not maximally differentiated.

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?

It gives an explicit trigger ('When a response says two agents' work collides (reconciliations_pending)') and a clear follow-up condition ('After the merge passes the tests, call again with resolve=[id]'), which sequences the two calls correctly. No explicit when-not guidance or named alternative is given, keeping it just below top marks.

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

All Collide MCP tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?