Skip to main content
Glama

Bulk Update Case Status

bulkUpdateCaseStatus
Destructive

Update the status of multiple cases to pending, completed, failed, or canceled. Interrupts any active runs and releases their case ownership, but never cancels their human-in-the-loop state — pending requests and open approval batches stay answerable/resolvable from the run view. Settling a case archives the pending requests on every run attached to it, both the runs this call interrupted and any that were already terminal, so they leave the activity inbox instead of outliving the case there. Resetting to pending archives nothing and re-dispatches cases to the queue's trigger consumer. Resetting cases on a paused queue answers 409, because it would interrupt runs the pause lets finish; resume the queue 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": {
      "queue_id": "<queue_id>",
      "status": "<status>"
    },
    "name": "bulkUpdateCaseStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoFree-text search selecting the cases when all_matching is true.
statusYesTarget status for each case. `completed`, `failed`, and `canceled` are terminal — `canceled` records a deliberate human stop, distinct from a system `failed`. `pending` resets the case (the queue's trigger consumer, if any, will re-claim it). `success` is not settable: it means an evaluation passed.
filtersNoFilters selecting the cases when all_matching is true.
case_idsNoExplicit case IDs to act on (1-100). Provide this or set all_matching.
queue_idYesThe queue's unique identifier
all_matchingNoWhen true, act on every case matching the provided filters/search instead of an explicit id list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / filters / properties / completed_at_from
      Added value: +{
      +  "description": "Keep Cases that reached an outcome at or after this time (inclusive). An ISO timestamp or a lookback such as `7d` or `12h`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / filters / properties / completed_at_to
      Added value: +{
      +  "description": "Keep Cases that reached an outcome before this time (exclusive). An ISO timestamp or a lookback such as `7d` or `12h`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / filters / properties / failure_source
      Added value: +{
      +  "description": "Keep only failed Cases, by who failed them: `system` when Duvo could not finish the Case, `manual` when a person marked it failed.",
      +  "items": {
      +    "enum": [
      +      "system",
      +      "manual"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / filters / properties / awaiting_my_approval
      Added value: +{
      +  "type": "boolean"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / filters / properties / created_at_to
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / filters / properties / json_data
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "operator": {
      +        "enum": [
      +          "equals",
      +          "notEquals",
      +          "in",
      +          "notIn",
      +          "gt",
      +          "gte",
      +          "lt",
      +          "lte",
      +          "contains",
      +          "isSet",
      +          "isNotSet"
      +        ],
      +        "type": "string"
      +      },
      +      "path": {
      +        "pattern": "^\\$(\\.[A-Za-z_][A-Za-z0-9_]{0,63})+$",
      +        "type": "string"
      +      },
      +      "value": {
      +        "anyOf": [
      +          {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "number"
      +              },
      +              {
      +                "type": "boolean"
      +              }
      +            ]
      +          },
      +          {
      +            "items": {
      +              "anyOf": [
      +                {
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "number"
      +                },
      +                {
      +                  "type": "boolean"
      +                }
      +              ]
      +            },
      +            "maxItems": 100,
      +            "minItems": 1,
      +            "type": "array"
      +          }
      +        ]
      +      }
      +    },
      +    "required": [
      +      "path",
      +      "operator"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 12,
      +  "type": "array"
      +}
    • addedInput schema / properties / filters / properties / updated_at_to
      Added value: +{
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Target status for each case. `completed` and `failed` are terminal; `pending` resets the case (the queue's trigger consumer, if any, will re-claim it)."New value: +"Target status for each case. `completed`, `failed`, and `canceled` are terminal — `canceled` records a deliberate human stop, distinct from a system `failed`. `pending` resets the case (the queue's trigger consumer, if any, will re-claim it). `success` is not settable: it means an evaluation passed."
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "pending",
      -  "completed",
      -  "failed"
      -]New value: +[
      +  "pending",
      +  "completed",
      +  "failed",
      +  "canceled"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / filters / properties / issue_severity
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "critical",
      +      "medium"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  6. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say destructive and non-idempotent; the description goes far beyond by disclosing that active runs are interrupted and lose case ownership, that human-in-the-loop requests remain answerable, that settling archives pending requests on all attached runs (including already-terminal ones), and that reset re-dispatches to the trigger consumer. It also exposes a specific failure mode (409 on paused queues) that no annotation carries.

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

Conciseness4/5

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

Front-loaded with purpose, then side effects, then the error case, with no filler sentences. Some sentences are long and clause-heavy (the archival sentence in particular), which slightly increases parsing cost but each still carries distinct behavioral information.

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?

For a six-parameter, nested-schema, destructive bulk mutation with no output schema, the description covers the important unknowns: side effects on runs and approvals, archival consequences, and the paused-queue error. It omits what the response returns and whether the operation is atomic or partially applied, which matters for a bulk destructive call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds consequence-level meaning for the status parameter: pending means reset plus re-dispatch, while terminal states archive pending requests. It does not add anything for all_matching, filters, or search, which the schema already documents.

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 (update) plus resource (case status) and enumerates the exact target values (pending, completed, failed, canceled). The 'multiple cases' framing plus queue/case_ids semantics distinguishes it from single-case siblings like updateCase without needing to name them.

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?

Gives concrete conditions: settling vs. resetting to pending produce different archival behavior, and resetting on a paused queue returns 409 with a prescribed remedy ('resume the queue first'). It stops short of explicitly comparing against single-case alternatives such as updateCase, so it is clear but not fully routing.

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.

Resources