Skip to main content
Glama

Collide MCP

by com.collidemcp.api
OverviewDiscussionsAdmin

recap

Read-only

What each agent did in this repo, session by session: edits, lines, tokens, model, estimated cost, rationales and top paths. Use it to answer "what happened" or "what did this cost". Read-only. Returns one entry per session and a dashboard link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days back, up to 90 (default 1).
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.

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"
-]New value: +[]
  2. Changed2 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"How many days back, up to 90 (default 1)."
    • addedInput schema / properties / repo_id / description
      Added value: +"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."
  3. Changed6 schema fields changed
    • removedInput schema / properties / days / default
      Removed value: -1
    • removedInput schema / properties / days / description
      Removed value: -"How many days of history to include."
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • 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: -"recapArguments"
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the repeated 'Read-only' line adds little. However, the description does disclose the return granularity ('one entry per session') and a dashboard link, which is real behavioral context not present in any structured field.

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?

Three tight sentences, front-loaded with the metric inventory before the usage hint and the return note. The 'Read-only' sentence is mildly redundant against the annotations, but nothing is padded or buried.

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 usefully compensates by naming the fields returned and the per-session granularity plus dashboard link. Combined with 100% schema coverage on the two optional params, an agent has enough to call it correctly; only minor gaps (auth/connection prerequisites) remain.

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 both parameters (days, repo_id) are already fully documented, including the 90-day cap and the repo_id format/default. The description only hints at repo scoping with 'in this repo' and adds no syntax or default 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 first sentence states precisely what the tool surfaces: per-session agent activity (edits, lines, tokens, model, cost, rationales, paths). That is a clear verb-plus-resource statement that resolves the opaque name 'recap'. It does not, however, explicitly differentiate itself from nearby siblings such as recall, remember, or get_briefing.

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 gives explicit trigger phrasings: use it to answer 'what happened' or 'what did this cost', which maps directly onto likely user intents. It offers no when-not guidance or named alternatives (e.g. recall for stored memory), so it stops short of full routing 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 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