Collide MCP

inbox_ack

Idempotent

Mark messages from teammates' agents as handled so they stop arriving: pass the ids from messages_pending once you have acted on them. Unacknowledged messages repeat on every response. Returns the messages still pending.

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": {
      "ids": "<ids>"
    },
    "name": "inbox_ack"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Message ids from messages_pending.
`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",
-  "ids"
-]New value: +[
+  "ids"
+]

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / ids / description

Added value: +"Message ids from messages_pending."

addedInput schema / properties / repo_id / description

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

Changed4 schema fields changedSep 18, 2026

removedInput schema / properties / ids / title
```
Removed value: -"Ids"
```

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 / title
```
Removed value: -"inbox_ackArguments"
```

First observedSep 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the description is not obligated to restate the safety profile. It does add genuinely new behavior: unacknowledged messages repeat on every response and the call returns the still-pending set, which is the motivation an agent needs. It omits what happens to unknown or already-acknowledged ids.

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?

Two sentences, front-loaded with the purpose and effect before the instruction. There is mild overlap between 'so they stop arriving' and 'Unacknowledged messages repeat on every response', but each still carries distinct information.

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 two-parameter acknowledgement tool with no output schema, the description covers purpose, input source, invocation timing, and the shape of the return. Missing error semantics on stale or unknown ids keep it from being fully complete.

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 coverage is 100%, so both ids and repo_id are already documented, including the repo_id default behavior. The description only restates that ids come from messages_pending and adds the timing cue 'once you have acted on them', which is baseline-level value over the schema.

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 (mark as handled), the resource (teammates' agent messages), and the observable effect (they stop arriving). It also points at the exact source of the input (messages_pending), so an agent can tell it apart from the listing sibling without opening the schema.

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?

Gives a clear usage condition: pass ids from messages_pending only after you have acted on them, which is exactly the decision an agent faces. It does not spell out what to do with ids that were never received or whether acknowledgement is mandatory, so it stops short of full when/when-not guidance.

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?