Skip to main content
Glama

Collide MCP

by com.collidemcp.api
OverviewDiscussionsAdmin

defer_intent

Leave work unfinished safely: a tripwire on paths or symbols that warns whoever next edits them (for example "webhooks in payments/ are half-done; finish them before changing this"). It fires once into their next tool result and briefing, and becomes a task in the team's CRM when one is connected. Returns the tripwire id and expiry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesWhat is unfinished and what the next person should do.
pathsNoFiles whose next edit triggers the warning.
repo_idNoThe repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in.
symbolsNoSymbol names whose next edit triggers it.
expires_daysNoDays until the tripwire expires (default 14).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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",
-  "note"
-]New value: +[
+  "note"
+]
  2. Changed5 schema fields changed
    • addedInput schema / properties / expires_days / description
      Added value: +"Days until the tripwire expires (default 14)."
    • addedInput schema / properties / note / description
      Added value: +"What is unfinished and what the next person should do."
    • addedInput schema / properties / paths / description
      Added value: +"Files whose next edit triggers the warning."
    • 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 / symbols / description
      Added value: +"Symbol names whose next edit triggers it."
  3. Changed20 schema fields changed
    • removedInput schema / properties / expires_days / default
      Removed value: -14
    • removedInput schema / properties / expires_days / description
      Removed value: -"How many days until this tripwire or intent expires."
    • removedInput schema / properties / expires_days / title
      Removed value: -"Expires Days"
    • removedInput schema / properties / note / description
      Removed value: -"The tripwire note to leave on the given paths/symbols."
    • removedInput schema / properties / note / title
      Removed value: -"Note"
    • removedInput schema / properties / paths / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / paths / default
      Removed value: -null
    • removedInput schema / properties / paths / description
      Removed value: -"Repo-relative file paths this change will touch."
    • addedInput schema / properties / paths / items
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / paths / title
      Removed value: -"Paths"
    • addedInput schema / properties / paths / type
      Added value: +"array"
    • 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 / symbols / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / symbols / default
      Removed value: -null
    • removedInput schema / properties / symbols / description
      Removed value: -"Symbol names referenced by, or being changed in, this edit."
    • addedInput schema / properties / symbols / items
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / symbols / title
      Removed value: -"Symbols"
    • addedInput schema / properties / symbols / type
      Added value: +"array"
    • removedInput schema / title
      Removed value: -"defer_intentArguments"
  4. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the one-shot firing behavior ('fires once into their next tool result and briefing'), the external side effect of creating a CRM task when connected (matching openWorldHint), and the return payload (tripwire id and expiry). This is rich, non-obvious behavioral context.

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 purpose, then layers mechanism, side effect, and return value in three tight sentences. The inline example is slightly long but earns its place by making the tripwire concept tangible.

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 five-parameter mutation tool with no output schema, the description covers purpose, firing behavior, side effects, and return values, which is nearly everything an agent needs. The only gap is the absence of when-not guidance relative to sibling memory/claim tools.

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 every parameter is already documented, and the baseline is 3. The description reinforces the paths/symbols trigger concept and mentions expiry in the return, but adds no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource: it creates a 'tripwire' on paths or symbols that warns the next editor. The concept is unmistakable and distinguishable from siblings like remember or claim, though no sibling is named explicitly to sharpen the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Leave work unfinished safely' implies the trigger condition (you are stopping mid-task), and the example note makes the intent concrete. However, it never states when to prefer this over remember/claim or when not to use it, leaving the agent to infer the boundary.

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