Skip to main content
Glama
rupturetrace-mcp

rupturetrace-mcp

by Susan571

compute_zigzag_h1

Computes zigzag H1 persistence over GF(2) for evolving graphs from ordered edge snapshots, returning Betti-1 values per snapshot and an interval barcode.

Instructions

Exact zigzag H1 persistence over GF(2) for an evolving graph.

snapshots: ordered edge-ID sets K_0..K_T; edges: [u, v] endpoints per edge ID; n_vertices: vertex count. Uses the diagram K_0 -> K_0 U K_1 <- K_1 -> ... and returns Betti-1 per node and the interval barcode.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "snapshots": "<snapshots>",
      "edges": "<edges>",
      "n_vertices": "<n_vertices>"
    },
    "name": "compute_zigzag_h1"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYes
snapshotsYes
n_verticesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the underlying construction (the diagram K_0 -> K_0 U K_1 <- K_1 -> ...), the field GF(2), and the exactness of the computation, plus what is returned. It omits error behavior, input validation rules, and any computational constraints.

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?

The purpose is front-loaded in the first line, followed by a compact parameter glossary and the output statement. Dense but nearly every sentence carries information; minor tightening is possible.

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?

No output schema exists, so the description appropriately states the return values itself, and it documents all three inputs despite an undocumented schema. Missing only edge-case behavior and validation constraints, which are secondary for a pure computation.

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 0%, so the description must compensate, and it largely does: it defines snapshots as ordered edge-ID sets K_0..K_T, edges as [u, v] endpoint pairs per edge ID, and n_vertices as the vertex count. Only edge-ID indexing relationships and validity constraints remain unstated.

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 uses a specific verb and resource ('compute zigzag H1 persistence over GF(2) for an evolving graph') and names the output (Betti-1 per node and interval barcode). It is clear to a domain reader, though the heavy jargon means an agent without TDA background gets less from it, and there is no sibling differentiation (none of the listed siblings are comparable).

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

Usage Guidelines2/5

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

Nothing states when to use this tool versus alternatives, nor any preconditions such as snapshot ordering consistency or valid edge-ID references. The intended usage is only implicit in the mathematical setup.

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