Skip to main content
Glama

Resume Paused Batch

alterlab_batch_resume

Resume a batch whose remaining items were paused with status paused_low_success because one domain or detector class kept failing (the machine-readable paused_reason says which). Use after the batch status shows paused items and you want them retried; items that failed were not charged. Returns batch_id, resumed (items re-enqueued) and status. Errors: nothing_to_resume, resume_in_progress, insufficient_credits.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "alterlab_batch_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYesbatch_id of the paused batch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that failed items were not charged, that the call re-enqueues items, that it returns batch_id/resumed/status, and that concurrent resumes surface resume_in_progress (consistent with idempotentHint=false). The credit and in-progress error modes are exactly the behavioral context an agent needs before invoking a non-read-only operation.

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?

Four sentences ordered purpose → when-to-use → return value → errors, with zero filler. The precondition is front-loaded so an agent can self-screen before reading further.

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?

There is no output schema, and the description compensates by naming the returned fields and all known error codes, which is sufficient for a single-parameter operational tool. Minor residual gap: it does not say whether a resumed batch can be paused again or how to poll its progress, though alterlab_batch likely covers status.

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?

Only one parameter, batch_id, and the schema already documents it at 100% coverage ('batch_id of the paused batch'). The description adds no format or sourcing guidance beyond that, so this sits at the documented baseline.

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?

Names a specific verb (resume) and resource (batch) plus the precise precondition: a batch paused with status paused_low_success because one domain or detector class kept failing. The paused_reason pointer makes it distinguishable from the sibling alterlab_batch without opening any schema.

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?

Explicit use condition: 'Use after the batch status shows paused items and you want them retried.' It does not name a contrasting sibling or state when not to resume, but the error list (nothing_to_resume, resume_in_progress, insufficient_credits) effectively scopes the invalid cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.