Collide MCP

send_agent_message

Send a message to teammates' agents. to = one account email; or anchor = the code it is about ("path.py::symbol", "path.py" or "dir/") with no to, which reaches whoever has an open intent on, or edited in the last day, that code or its callers. With an anchor the recipient also sees whether the code changed since you sent it and whether its tests have passed since. It arrives with their next tool result. Returns the message id and who received it.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	A teammate's account email; omit it when anchor is given.
`anchor`	No	The code the message is about: path.py::symbol, path.py, or dir/.
`message`	Yes	What you need them to do or know.
`repo_id`	Yes	The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 27, 2026

addedInput schema / properties / anchor / description

Added value: +"The code the message is about: path.py::symbol, path.py, or dir/."

addedInput schema / properties / message / description
```
Added value: +"What you need them to do or know."
```

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

Added value: +"A teammate's account email; omit it when anchor is given."

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / anchor
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / required

Previous value: -[
-  "repo_id",
-  "to",
-  "message"
-]New value: +[
+  "repo_id",
+  "message"
+]

Changed5 schema fields changedSep 18, 2026

removedInput schema / properties / message / title
```
Removed value: -"Message"
```

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

removedInput schema / title

Removed value: -"send_agent_messageArguments"

First observedSep 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations mark this as a non-destructive write, but the description adds delivery mechanics (arrives with their next tool result), recipient-side context (they see whether the code changed and whether tests passed since), and return values (message id and recipient). This is meaningful behavior far beyond the annotation set.

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 the two routing modes and keeps every clause informative, though the anchor sentence is dense enough that it takes a second read to parse the recipient-selection rule.

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 covers return values, delivery timing, and both routing paths, so 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.

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 real semantics beyond the schema: the anchor resolution rule (open intent or last-day edits, including callers) is not captured in the schema's terser 'path.py::symbol, path.py, or dir/' text.

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 (send) and resource (message to teammates' agents) and immediately disambiguates the two routing modes (to vs anchor). An agent can distinguish this from siblings like connect_agents or inbox_ack 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly defines the selection conditions: use `to` with one account email, or use `anchor` alone (no `to`) to reach whoever has an open intent on or recently edited the code or its callers. This is genuine when/how-to-use guidance, not implied.

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?