Skip to main content
Glama

job_rollback

Undo a delegated job by restoring every changed file to its pre-job content. Batch tasks are reverted newest first.

Instructions

Undo a delegated job: every file it changed goes back to its content before the job. For a batch, every task is undone, newest first.

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": {
      "job_id": "<job_id>"
    },
    "name": "job_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

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 itself discloses the mutating scope: all files changed by the job are restored to their pre-job content. It also adds useful batch behavior—all tasks are undone, newest first—but leaves later edits, created or deleted files, non-file side effects, and partial failures unaddressed.

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?

Two short sentences front-load the operation and its file-restoration scope, then add only the relevant batch rule. There is no filler or redundancy.

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 one-parameter tool with an output schema, the core action and batch behavior support a basic invocation without needing return-value documentation. However, a rollback operation with no annotations needs more context about valid job states, safety limitations, and conflict or failure behavior to be fully reliable.

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?

The schema provides only the name job_id and no parameter description. The prose narrows it to a delegated job and implies batch rollback is supported, but does not explain the expected identifier form, where to obtain it, or whether a batch identifier is passed in the same field.

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?

“Undo a delegated job” supplies a specific verb and resource, and “every file it changed goes back to its content before the job” makes the effect concrete. It clearly conveys reversal rather than inspection or continuation, but does not explicitly differentiate itself from any sibling workflow.

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?

The wording implies use after a delegated job when its file changes should be reversed, and the second sentence covers batches. It provides no explicit prerequisites, eligible job states, when-not-to-use conditions, or alternatives.

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