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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recall"
  }
}

Input 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 Cork briefing names it). Omit it to use the repo your session works in.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / repo_id / description

Previous 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."New value: +"The repository id, e.g. github.com/org/repo (the Cork briefing names it). Omit it to use the repo your session works in."

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 cover the safety profile (readOnlyHint, destructiveHint, openWorldHint), so 'Read-only' is redundant. The description still adds real behavior: newest-first ordering, the empty-query fallback, and the return shape ('anchor, confidence and whether it may be stale'). It stops short of anything about result volume or how staleness is determined.

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?

Three front-loaded sentences that each carry weight: what it searches, when to use it versus the briefing, and what comes back. The only wasted clause is 'Read-only,' which merely repeats the readOnlyHint annotation.

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?

With no output schema, the description compensates by naming the returned fields (anchor, confidence, staleness) and the ordering. Combined with the explicit sibling routing and the empty-query default, an agent has everything needed to call it 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 all four parameters are already documented, including the AND semantics of tags and the repo_id default. The description only restates the empty-query behavior that the query parameter already documents, adding no new syntax or format guidance.

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 ... by text and tags'), names the creating sibling ('made with remember'), and specifies ordering and the empty-query fallback. An agent can distinguish this from remember (write) and get_briefing (hook briefing) without opening any 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 scopes use: '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.' That gives both a when-not (notes already in the briefing) and a when (searching beyond them before re-litigating a settled decision).

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?