Skip to main content
Glama
rupturetrace-mcp

rupturetrace-mcp

by Susan571

verify_run

Verifies a RuptureTrace output directory offline by recomputing diagnostics, derived files, and hashes to check record consistency and, optionally, claim/ID linkage against the original input.

Instructions

Verify a RuptureTrace output directory offline: recompute diagnostics, derived files and hashes.

Checks record consistency only - not scientific truth. input_path optionally points to the original claim JSONL to check claim/ID linkage. Runs produced in host mode cannot be replay-verified.

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": {
      "directory": "<directory>"
    },
    "name": "verify_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYes
input_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 useful work by declaring the operation is offline, recomputes derived files and hashes, and refuses host-mode runs. It does not say whether recomputing derived files writes to disk, whether the operation is read-only or destructive, or what happens when a check fails, which are meaningful gaps for a verification tool that touches a directory.

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?

Four short sentences, front-loaded with the core action and scope, then the key limitation, then parameter meaning. No filler, though the final limitation sentence would read more naturally attached to the verification claim it qualifies rather than trailing at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, scope limits, and both parameters for a two-parameter tool with no annotations and no output schema. Still missing what a verification result contains (pass/fail shape, per-check detail) and whether the directory is modified, which an agent needs before calling a recompute-and-hash tool.

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 0%, so the description must compensate for two parameters. It explains input_path well (original claim JSONL, used for claim/ID linkage) and 'directory' is inferable from 'RuptureTrace output directory' in the opening sentence, but neither parameter gets format, path-resolution, or default-behavior detail beyond that.

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 specific verb and resource ('Verify a RuptureTrace output directory offline') and immediately bounds the scope: 'recompute diagnostics, derived files and hashes' plus 'Checks record consistency only - not scientific truth.' That second clause distinguishes it from sibling tools like evaluate_run and assess_claim, which plausibly judge scientific content rather than record integrity.

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?

Gives a clear condition for use (offline verification of an output directory) and an explicit exclusion ('Runs produced in host mode cannot be replay-verified'), plus a conditional use for the optional parameter ('input_path optionally points to the original claim JSONL to check claim/ID linkage'). It does not name a specific alternative tool to use for scientific evaluation, 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.