Duvo MCP

Bulk Reprocess Cases

bulkReprocessCases

Re-process multiple cases on a chosen agent. Any active runs on the selected cases are interrupted first; the cases are then reset to pending and assigned to the chosen agent for the next dispatcher tick. The chosen agent must already be connected to the queue as a case-queue-consumer (with the trigger enabled or disabled) and not belong to a different automation than the queue.

Input Schema

TableJSON Schema

Name	Required	Description
`search`	No	Free-text search selecting the cases when all_matching is true.
`filters`	No	Filters selecting the cases when all_matching is true.
`agent_id`	No	The agent that should run on the selected cases. Must be a consumer of this queue and not belong to a different automation.
`case_ids`	No	Explicit case IDs to act on (1-100). Provide this or set all_matching.
`queue_id`	Yes	The queue's unique identifier
`all_matching`	No	When true, act on every case matching the provided filters/search instead of an explicit id list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / agent_id / description

Previous value: -"The agent that should run on the selected cases. Must be a consumer of this queue."New value: +"The agent that should run on the selected cases. Must be a consumer of this queue and not belong to a different automation."

Changed1 schema field changedSep 14, 2026
- addedInput schema / properties / filters / properties / awaiting_my_approval
```
Added value: +{
+  "type": "boolean"
+}
```

Changed3 schema fields changedSep 8, 2026

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"
+}
```

Changed1 schema field changedAug 18, 2026

addedInput schema / properties / filters / properties / issue_severity

Added value: +{
+  "items": {
+    "enum": [
+      "critical",
+      "medium"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

First observedAug 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, and idempotent=false, but the description adds the crucial mutation sequence: active runs are interrupted, cases reset to pending, and assigned for the next dispatcher tick. It also discloses the agent's queue-connection prerequisite. It does not cover permissions or rate limits, but adds substantial behavioral context beyond annotations.

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?

Three sentences, front-loaded with purpose, then behavior, then prerequisites. Every sentence earns its place and there is no filler.

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 bulk mutation tool with no output schema but rich annotations and full parameter descriptions, the definition covers purpose, side effects, and key prerequisites. It could mention returned status or confirmation, but the structured fields carry most of the remaining burden.

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%; all six parameters, including nested filters, have descriptions. The tool description does not add parameter syntax, defaults, or format details beyond what the schema already provides, so it merits the baseline for high coverage.

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?

The description opens with a specific verb and resource ('Re-process multiple cases on a chosen agent') and specifies the selection scope. Its stated side effects (interrupting runs, resetting to pending, reassigning) distinguish it from sibling bulk status/priority updaters.

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?

It explains what will happen when called, but does not state when to choose this over alternatives such as bulkUpdateCaseStatus or startRun. The prerequisite about the agent being a connected case-queue-consumer is useful context, not a when-to-use rule.

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

All Duvo MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?