Skip to main content
Glama
Jackxiaozhiren

datasentry

by Jackxiaozhiren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

repair_rollback_batch

Destructive

Roll back applied repairs by run ID, restoring pre-repair snapshots and returning rolled-back runs plus per-run errors; writes only when confirmed.

Instructions

Roll back applied repairs by run id. WRITES DATA: restores the pre-repair snapshot for each run. Returns rolled-back runs and per-run errors.

Input Schema

NameRequiredDescriptionDefault
confirmYesmandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)
repair_run_idsYesrepair run ids (e.g. rep_xxx)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "mandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "repair_run_ids"
-]New value: +[
+  "repair_run_ids",
+  "confirm"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with "WRITES DATA" plus the specific effect (restores the pre-repair snapshot). It also discloses return shape (rolled-back runs and per-run errors), adding useful context beyond annotations.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the mutation warning ("WRITES DATA") before the effect and return values. Zero wasted words.

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?

Covers mutation semantics, the confirm gate, effect, and return values for a 2-param tool with no output schema. Minor gap: no mention of irreversibility or idempotency behavior.

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%, with both parameters—including the confirm gate—fully documented in the schema. The description adds only "by run id" and per-run errors, so the schema does the heavy lifting; baseline 3 fits.

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 ("Roll back") and resource ("applied repairs by run id"), clearly distinguishing it from siblings like repair_apply_batch and repair_propose_batch. An agent can tell exactly what this does.

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

Usage Guidelines3/5

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

Implies usage after repairs have been applied ("Roll back applied repairs"), but offers no explicit when-to-use/when-not or named alternatives such as repair_apply_batch as the inverse operation.

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

Deploy Server

Other Tools