Collide MCP

recall

Read-only

Search the team's saved notes (made with remember) by text and tags, newest first; an empty query returns the most recent. The hook briefing already carries the notes anchored to the code you touch: use this only to search beyond them, before re-deciding something the team may already have settled. Read-only. Returns each note with its anchor, confidence and whether it may be stale.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Only notes carrying all of these tags.
`limit`	No	Maximum notes to return (default 25).
`query`	No	Text to find in the note; empty returns the most recent.
`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.

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: +[]

Changed4 schema fields changedSep 27, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum notes to return (default 25)."

addedInput schema / properties / query / description

Added value: +"Text to find in the note; empty returns the most recent."

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 / tags / description

Added value: +"Only notes carrying all of these tags."

Changed13 schema fields changedSep 18, 2026
- removedInput schema / properties / limit / default
```
Removed value: -25
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / query / default
```
Removed value: -""
```
- removedInput schema / properties / query / title
```
Removed value: -"Query"
```
- 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 / tags / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / tags / default
```
Removed value: -null
```
- removedInput schema / properties / tags / description
```
Removed value: -"Optional labels to categorize this memory."
```
- addedInput schema / properties / tags / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / tags / title
```
Removed value: -"Tags"
```
- addedInput schema / properties / tags / type
```
Added value: +"array"
```
- removedInput schema / title
```
Removed value: -"recallArguments"
```
First observedSep 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds non-obvious behavior: empty query returns the most recent, results are ordered newest first, and each note comes back with anchor, confidence and a staleness flag. It does not discuss rate limits or result truncation, so it falls short of a 5.

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-loads what the tool does and follows with the usage constraint, so the important routing information comes first. It is dense and slightly overpacked — three ideas separated by semicolons — but no sentence is filler.

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?

There is no output schema, and the description compensates by naming the returned fields (anchor, confidence, staleness). Combined with the ordering, empty-query behavior, and the note-creation sibling, an agent has everything needed to call and interpret this 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?

Schema description coverage is 100%, so tags, limit, query and repo_id are already documented, including the empty-query fallback and the repo_id omission default. The description adds only the 'newest first' ordering, which the schema does not state — enough to hold the baseline of 3 but not to exceed it.

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 (search the team's saved notes) plus the matching mechanism (by text and tags) and ordering (newest first). It also names the sibling tool that produces the data (remember), so an agent can place it in the workflow without opening a schema.

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?

Explicitly says when NOT to use it — the hook briefing already carries notes anchored to the code you touch — and when to reach for it instead: searching beyond those anchors, before re-deciding something the team may already have settled. That is a clear when/when-not/alternative triad.

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?