Collide MCP

remember

Save a durable team fact: a decision, constraint or gotcha, not code state. Anchor facts about specific code (anchor="auth.py::validate_token", "auth.py" or "src/auth/"): anchored notes reach whoever touches that code and are marked stale when it is rewritten. Writes the note(s) and returns their ids.

Input Schema

TableJSON Schema

Name	Required	Description
`fact`	No	The note, one or two sentences.
`tags`	No	Labels to find it by with recall.
`facts`	No	Several notes at once: [{fact, anchor?, tags?}].
`anchor`	No	Where it applies: path::symbol, a file, or dir/.
`repo_id`	Yes	The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json).
`supersedes`	No	Id of a note this one replaces; the old note is retired.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 27, 2026

addedInput schema / properties / anchor / description

Added value: +"Where it applies: path::symbol, a file, or dir/."

addedInput schema / properties / fact / description
```
Added value: +"The note, one or two sentences."
```

addedInput schema / properties / facts / description

Added value: +"Several notes at once: [{fact, anchor?, tags?}]."

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

Added value: +"Id of a note this one replaces; the old note is retired."

addedInput schema / properties / tags / description

Added value: +"Labels to find it by with recall."

Changed2 schema fields changedSep 18, 2026

addedInput schema / properties / facts

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / required

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

Changed17 schema fields changedSep 18, 2026
- removedInput schema / properties / anchor / default
```
Removed value: -""
```
- removedInput schema / properties / anchor / description
```
Removed value: -"Pin this memory to specific code: 'path.py::symbol', 'path.py', or 'src/dir/'."
```
- removedInput schema / properties / anchor / title
```
Removed value: -"Anchor"
```
- removedInput schema / properties / fact / description
```
Removed value: -"The durable fact or decision to remember."
```
- removedInput schema / properties / fact / title
```
Removed value: -"Fact"
```
- 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 / supersedes / default
```
Removed value: -""
```
- removedInput schema / properties / supersedes / description
```
Removed value: -"The id of a prior memory this note replaces."
```
- removedInput schema / properties / supersedes / title
```
Removed value: -"Supersedes"
```
- 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: -"rememberArguments"
```
First observedSep 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare a non-destructive write, and the description adds real behavioral context: anchored notes surface to whoever touches that code, get marked stale on rewrite, and supersedes retires the old note. That goes well beyond the safety hints, though nothing is said about rate limits or write conflicts.

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 dense sentences, front-loaded with the core purpose and the key distinction from code state. Every clause carries information, though the anchoring detail is packed tightly enough to require a second read.

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?

For a 6-parameter write tool with no output schema, the description covers purpose, anchoring semantics, batching implication, and return value ('returns their ids'). Minor gaps remain around tag conventions and batch limits on facts.

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 the baseline is 3, but the description adds meaning beyond the schema: it explains the operational consequence of anchor (reaching code touchers, staleness) and the retirement behavior of supersedes. The anchor form examples reinforce the schema's field syntax.

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 ('Save a durable team fact') and sharply scopes the content ('a decision, constraint or gotcha, not code state'). The explicit exclusion of code state distinguishes it from retrieval siblings like recall and recap.

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?

Clear guidance on what to store and when to anchor ('facts about specific code'), with concrete anchor syntax examples. It does not explicitly name recall as the counterpart read tool, so the routing is implied rather than stated.

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?