Skip to main content
Glama

migration_resumeBatch

Resume one or more suspended migration batches by ID to continue interrupted migrations and return per-batch success or error results.

Instructions

Resume one or more suspended migration batches by ID. Returns per-batch success or error.

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": {
      "batchIds": "<batchIds>"
    },
    "name": "migration_resumeBatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchIdsYesBatch IDs to resume

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / batchIds
      Added value: +{
      +  "description": "Batch IDs to resume",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / required
      Added value: +[
      +  "batchIds"
      +]
  2. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the return shape as per-batch success or error, which usefully signals that partial failure is possible across a batch list. It omits permissions required, idempotency of repeated resumes, and behavior when an ID is unknown or not currently suspended.

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, zero filler, with the action front-loaded and the return contract in the second sentence. Nothing could be removed without losing information.

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 mutation tool this covers the action and the response shape, which is close to sufficient given there is no output schema. Missing are the failure and edge-case semantics (unknown ID, already-running batch, permission errors) that an agent would need to interpret the per-batch errors it is told to expect.

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?

The single parameter is fully documented in the schema at 100% coverage, so baseline 3 applies. The description adds only 'by ID' and the plurality implied by 'one or more', which the array type already conveys.

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?

States a specific verb (resume) and resource (suspended migration batches) with the ID-based scope, and the word 'suspended' implicitly separates it from migration_suspendBatch and migration_executeBatch. It never names a sibling explicitly, so an agent must still infer the contrast rather than being routed to it.

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 precondition 'suspended' implies when this tool applies, which is enough to select it over executeBatch in most cases. There is no explicit when-not guidance, no mention of what to do if a batch is not suspended, and no named alternatives for the retry/status workflows that surround it.

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