Duvo MCP

Bulk Update Case Priority

bulkUpdateCasePriority

Destructive

Set the priority of multiple cases. Priority only affects the order pending cases are picked up in: due postponed cases are handled first, then higher priority. It never interrupts runs or changes case status. Set none to clear priority back to the default.

Input 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.
`case_ids`	No	Explicit case IDs to act on (1-100). Provide this or set all_matching.
`priority`	Yes	Target priority for each case. `medium`/`high` raise it above the default; `none` clears it.
`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.

Changed3 schema fields changedOct 12, 2026

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

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.2/5.0

Behavior4/5

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

Annotations already declare the write/destructive profile, and the description adds genuinely new semantics: priority ordering (due postponed cases first, then higher priority), that it never interrupts runs or changes status, and that `none` resets to default. It does not cover auth needs, bulk size limits, or partial-failure behavior, so it falls short of 5.

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 tight sentences with no filler; the core action is front-loaded and the qualifiers (ordering semantics, non-disruption, reset) each earn their place.

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, the description covers the effect and its boundaries well. Minor gaps remain around bulk limits and per-case failure handling, but the essential behavior is conveyed.

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 description coverage is 100%, so all six parameters are documented in the schema; the description re-explains the `priority` enum values and the `none` reset, which adds some but not substantial meaning beyond the schema. Baseline 3 applies.

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 and resource ('Set the priority of multiple cases') with the 'bulk/multiple' scope explicit. It distinguishes itself from the nearest sibling, bulkUpdateCaseStatus, by stating it 'never ... changes case status', so an agent can separate the two without reading schemas.

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?

Explains the operational context (priority governs pickup order for pending cases) and implicitly routes away from status mutation, giving clear when-to-use context. It stops short of an explicit 'use X instead when Y' exclusion statement, so it is not a full 5.

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?