iSuite Operations MCP Server

rerun_batch

Re-execute a failed or cancelled batch job with optional parameter overrides. Resume from the failed step or restart entirely.

Instructions

Re-execute a failed or cancelled batch job, optionally with parameter overrides.

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": {
      "batchId": "<batchId>"
    },
    "name": "rerun_batch"
  }
}

Input Schema

Name	Required	Description
`batchId`	Yes	The batch execution ID to rerun.
`fromFailedStep`	No	Resume from the failed step rather than restarting entirely (default true).
`overrideParams`	No	Optional parameter overrides for the re-run.
`priority`	No	Execution priority for the re-run (default 'normal').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses re-execution with overrides but does not specify side effects, authorization needs, or what happens to the original batch. Minimal but adequate.

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?

Single sentence with no wasted words, front-loaded essential information. Perfectly concise.

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?

Simple tool with 4 params and no output schema, description covers core purpose but lacks details on return values or post-rerun behavior. Still adequate for straightforward use.

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 coverage is 100%, and description adds little beyond saying 'with parameter overrides'. Schema already documents each param well; description provides no further detail on behavior of fromFailedStep or priority.

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?

Description clearly states the verb 'Re-execute' and resource 'failed or cancelled batch job', with optional parameter overrides. It effectively distinguishes this tool from siblings like retry_job and cancel_batch.

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?

Explicitly states when to use (for failed/cancelled batch jobs) and mentions optional overrides, but lacks comparison to alternatives like retry_job or conditions where it should not be used.

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