Skip to main content
Glama

Collide MCP

by com.collidemcp.api
OverviewDiscussionsAdmin

claim

Reserve the next number in a sequence (a migration, an ADR, a release) so no other agent takes it; two agents asking at once never get the same number. The hooks already claim a numbered file's number when you create it, so call this only for a number you need before writing, or for a named sequence. Returns the number, zero-padded like the files already there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoThe highest number you already see in use in that directory, if any.
titleNoWhat the number is for; teammates see it.
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.
sequenceYesA directory such as db/migrations/, or a name such as release.

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",
-  "sequence"
-]New value: +[
+  "sequence"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / after / description
      Added value: +"The highest number you already see in use in that directory, if any."
    • 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 / sequence / description
      Added value: +"A directory such as db/migrations/, or a name such as release."
    • addedInput schema / properties / title / description
      Added value: +"What the number is for; teammates see it."
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations establish the safety profile (readOnlyHint=false, destructiveHint=false), so the bar is lower, and the description still adds real value: it discloses the concurrency guarantee ("two agents asking at once never get the same number"), the return format (zero-padded number), and the interaction with the create-file hooks. Gaps remain on reservation lifetime/expiry and what happens if a number is already taken, but this is well above the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action and scope, then the when-to-use constraint, then the return shape. No filler; each sentence carries distinct information an agent needs.

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?

With no output schema, the description correctly explains the return value (the padded number), and the mutating semantics are covered by annotations plus the reservation explanation. What is missing for a state-changing reservation tool is the failure/expiry behavior, but everything needed to make a correct call is present.

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 in the schema, including that `sequence` may be a directory or a name. The description echoes the "named sequence" case and the zero-padding but adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 concrete verb and resource ("Reserve the next number in a sequence") and pins the scope with examples of what a sequence is: a migration, an ADR, a release. It also names the side effect (concurrency-safe reservation), so an agent knows exactly what it gets. No sibling in the list overlaps with this function, so disambiguation is not an issue.

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?

Explicit when-to-use: "call this only for a number you need before writing, or for a named sequence." Explicit when-not: the hooks already claim a numbered file's number when you create it, so a plain file creation needs no claim. The alternative path (hooks on file creation) is named, leaving little to inference.

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