Skip to main content
Glama
rupturetrace-mcp

rupturetrace-mcp

by Susan571

start_host_assessment

Starts a RuptureTrace assessment for a scientific claim by returning the first stage prompt and guiding the client model through submission rounds until diagnostics and repair relations are computed.

Instructions

Start a RuptureTrace assessment where YOU (the MCP client model) produce each round.

Returns the first stage prompt (instructions, input payload and output schema). Answer every step with submit_host_round until status is 'completed' (7 steps; 9 with ablation). The server computes support, zigzag H1 persistence and the repair relation itself. If out_dir is set, artifacts are written at the end.

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": {
      "claim": "<claim>"
    },
    "name": "start_host_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes
out_dirNo
overwriteNo
with_h1_ablationNo
allow_source_fetchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose real behavior: the server itself computes support, zigzag H1 persistence and the repair relation, and artifacts are written at the end only if out_dir is set. Undisclosed are the effects of overwrite and allow_source_fetch (which implies network fetching) and what happens if a run is abandoned mid-protocol.

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

Conciseness3/5

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

Front-loaded and only three sentences, which is appropriately sized for a multi-step protocol. However, the formatting (line breaks mid-sentence, parenthetical digressions) slightly obscures the two-and-fro structure instead of presenting "what it returns" and "how to continue" as clean, scannable statements.

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?

For a workflow-launching tool with no output schema, it does describe the return value (stage prompt with instructions, input payload and output schema) and the termination condition. It is still incomplete on the two behavioral flags and on overwrite/restart semantics, which an agent needs before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across five parameters, so the description must compensate and largely does not. out_dir is explained (artifacts written at the end) and "with ablation" maps to with_h1_ablation, but claim, overwrite and allow_source_fetch get no meaning at all — the latter two are the ones most likely to cause unintended side effects or network access.

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?

"Start a RuptureTrace assessment" gives a specific verb and resource, and the clause "where YOU (the MCP client model) produce each round" clarifies the unusual client-driven protocol. It does not name a sibling to contrast with (e.g. assess_claim), so differentiation is left to inference, but the purpose itself is unambiguous.

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?

It gives an explicit operating loop: answer each step with submit_host_round and stop when status is 'completed', with the step count (7, or 9 with ablation) so the agent knows the workload. It stops short of saying when to prefer this over assess_claim/assess_claims_batch, so the when-not guidance is missing.

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