Skip to main content
Glama

Collide MCP

by com.collidemcp.api
OverviewDiscussionsAdmin

connect_agents

Set up Collide for the agent tools on this machine (Claude Code, Codex, Cursor, Hermes): returns the same one install command as setup, which installs Collide's hooks once for every repo on the machine and writes nothing into the repo. mode "files" returns the protocol rules files and MCP configs to commit for tools without hooks (Windsurf, Cline, GitHub Copilot) instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoLeave empty for the machine install; "files" for the rules files and MCP configs.
repo_idYesThe repository id, e.g. github.com/org/repo (repo_id in .collide/config.json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Leave empty for the machine install; \"files\" for the per-repo files."New value: +"Leave empty for the machine install; \"files\" for the rules files and MCP configs."
  2. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "Leave empty for the machine install; \"files\" for the per-repo files.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / repo_id / description
      Added value: +"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."
  4. Added
  5. Removed
  6. Changed3 schema fields changed
    • 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: -"connect_agentsArguments"
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare this is not read-only but non-destructive and not open-world; the description adds real behavioral context beyond them, disclosing that it installs hooks once for every repo on the machine and writes nothing into the repo, and that it returns an install command rather than performing everything silently. Missing permission/auth prerequisites and whether anything is written outside the repo.

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?

Effectively one dense sentence that front-loads the primary action and then the alternative mode. It is appropriately sized for a two-mode tool, though the parenthetical tool lists make it slightly heavy to scan.

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 tool with no output schema, the description covers what both modes return and the machine-wide side effect, which is enough for correct invocation. Auth requirements and the exact shape of the returned files list are the only notable omissions.

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 goes further by explaining what mode="files" actually yields (protocol rules files and MCP configs to commit) and which tools need them, adding meaning beyond the schema's terser mode note.

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 ("Set up Collide for the agent tools on this machine"), names the concrete tools it targets, and explicitly differentiates itself from the sibling `setup` by describing what it returns relative to it. An agent can distinguish this from setup and from other siblings 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 Guidelines4/5

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

The description clearly splits the two modes: empty mode for the machine install, "files" for tools without hooks, listing which tools fall in each camp (Claude Code/Codex/Cursor/Hermes vs Windsurf/Cline/Copilot). It gives context but does not state when to prefer this over the sibling `setup`, despite referencing it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Collide MCP toolsInspect
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