Duvo MCP

Export Cases

exportCases

Export a queue's cases, respecting the same status, severity, failure source, approval, priority, label, date-range, json_data field, and free-text filters as the list view. Set awaiting_my_approval to export only the cases holding an unanswered approval row assigned to you; like the list view it resolves to the authenticated caller, so a credential with no user behind it is rejected rather than exporting an empty file. format: "json" (default) returns a re-importable JSON payload; format: "csv" returns a text/csv file with the columns id, title, status, priority, labels, created_at, updated_at, completed_at, postponed_to, data.

Input Schema

Name	Required	Description	Default
`format`	No		json
`search`	No
`filters`	No
`sort_by`	No		created_at
`queue_id`	Yes	The queue's unique identifier
`sort_order`	No		asc

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

AddedSep 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds real behavioral context beyond annotations: default vs csv format outputs, the exact csv column set, re-importability of the JSON payload, and the failure behavior for credential-less callers. Annotations are present but poorly suited to this operation (readOnlyHint=false and idempotentHint=false on an export), and the description does not address that mismatch, leaving a small gap.

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?

Three sentences, front-loaded with the core export semantics before the edge-case credential behavior and the format details. Dense but every clause carries information; the credential-rejection clause is niche but genuinely useful for avoiding a silent empty export.

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?

No output schema exists, and the description compensates by describing the JSON payload as re-importable and listing the csv columns. Given a nested filters object and 6 parameters, it covers most of what a caller needs, but omits sorting behavior and any size/async-export limits that a large export would hit.

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?

With only 17% schema description coverage, the description must carry the parameter burden, and it largely does: it enumerates the filter families (status, severity, failure source, approval, priority, label, date-range, json_data, free-text), pins down awaiting_my_approval, and explains both format values. It says nothing about sort_by/sort_order or the date-range syntax, so the compensation is not complete.

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 — 'Export a queue's cases' — with the scope (single queue) and the two output shapes spelled out. This clearly differentiates it from listCases/searchCases (viewing) and from unrelated export siblings like exportPulseDashboardHtml. An agent can identify the tool's function without opening the 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?

It anchors usage by stating the filters mirror 'the list view' and describes the one non-obvious selector, awaiting_my_approval, including the credential prerequisite (a caller with no user is rejected rather than producing an empty file). However it never explicitly says when to choose export over listCases or searchCases, so the routing is implied rather than stated.

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?