Tools for agents: Vector-clock comparison and merge

Connect with MCP

{
  "mcpServers": {
    "super-agent-tools": {
      "url": "https://app.getsupers.com/sites/agent-vector-clock/mcp"
    }
  }
}

Use this URL in any client supporting remote Streamable HTTP MCP. Calls return structured JSON; inputs are processed without persistence.

Call compare_vector_clocks

Relation describes left relative to right: before means every left counter is <= right and at least one is smaller; after is the reverse; equal means all components match; concurrent means each clock is ahead on at least one actor. Absent actors count as zero. Empty clocks are allowed and equal explicit all-zero clocks. Actor IDs are case-sensitive exact strings; counters must be nonnegative JSON integers, not booleans or decimal numbers. The merged clock contains the union of actors, including explicit zero entries, with componentwise maximum counters. It does not increment any actor, merge payloads, resolve semantic conflicts, authenticate history, or persist state. Causal interpretation requires clocks maintained correctly under a shared actor identity scheme; supplied counters alone cannot prove actual event history. Clock timestamps are not wall-clock times. Do not truncate actors if exact comparison is required. Background: https://www.allthingsdistributed.com/2007/10/amazons_dynamo.html

{
  "name": "compare_vector_clocks",
  "title": "Vector-clock comparison and merge",
  "description": "Compare componentwise nonnegative vector clocks, treating absent actors as zero. Return equal/before/after/concurrent, witnesses and merged maximum counters. Does not increment counters or merge payloads.",
  "inputSchema": {
    "properties": {
      "left": {
        "additionalProperties": {
          "type": "integer"
        },
        "title": "Left",
        "type": "object"
      },
      "right": {
        "additionalProperties": {
          "type": "integer"
        },
        "title": "Right",
        "type": "object"
      }
    },
    "required": [
      "left",
      "right"
    ],
    "title": "compare_vector_clocksArguments",
    "type": "object"
  },
  "outputSchema": {
    "additionalProperties": true,
    "title": "compare_vector_clocksDictOutput",
    "type": "object"
  },
  "icons": null,
  "annotations": {
    "title": null,
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false
  },
  "meta": null,
  "execution": null
}

Run the example to see the actual result.

HTTP alternative

POST https://app.getsupers.com/sites/agent-vector-clock/call
Content-Type: application/json

{
  "left": {
    "builder": 3,
    "reviewer": 1
  },
  "right": {
    "builder": 2,
    "reviewer": 2
  }
}

The HTTP and MCP interfaces execute the same implementation. Validation errors are returned explicitly. See the tool notes above for its supported inputs and behavior.