Skip to main content
Glama

Duvo MCP

by io.github.duvoai
OverviewDiscussionsAdmin

Update Case

updateCase
Destructive

Edit a case's title and/or its data payload. Provide at least one field. For the payload, send free-form data OR a structured json_data object, never both. json_data is validated against the queue's Case schema and requires the queue to have one; a case that is already typed against a schema keeps its structured payload and rejects a free-text data write. Works on pending, in-progress, and settled cases. Other attributes (status, priority, labels) have their own dedicated endpoints. Returns the updated case with its event history and approval batches.

Input Schema

NameRequiredDescriptionDefault
dataNoNew free-form data payload handed to the agent when the case is claimed. Mutually exclusive with `json_data`.
titleNoNew case title (1–500 characters).
case_idYesThe case's unique identifier
json_dataNoNew structured payload for a case on a queue that has a Case schema. Validated against that schema and mutually exclusive with `data`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / data / description
      Previous value: -"New free-form data payload handed to the agent when the case is claimed."New value: +"New free-form data payload handed to the agent when the case is claimed. Mutually exclusive with `json_data`."
    • addedInput schema / properties / json_data
      Added value: +{
+  "additionalProperties": {},
+  "description": "New structured payload for a case on a queue that has a Case schema. Validated against that schema and mutually exclusive with `data`.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only carry the safety flags (destructive=true, idempotent=false); the description adds substantive behavior beyond them: json_data is validated against the queue's Case schema and requires that schema to exist, and a schema-typed case rejects a free-text data write. It also discloses the return contents (updated case with event history and approval batches).

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-loads the core action and required-field constraint, then layers the payload rules and exclusions. Every sentence carries information, though the mutual-exclusivity point is stated twice (once in prose, once reinforced), making it slightly denser than strictly necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with no output schema, but the description covers return values (updated case plus event history and approval batches), the payload constraints, applicability across case states, and the sibling routing. Nothing an agent needs to invoke it correctly is missing.

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 the baseline is 3 and the schema already documents each field. The description adds real value on top: the never-both rule, the queue-must-have-a-schema requirement for json_data, and the type-locking behavior that rejects data writes on schema-typed cases.

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 (edit) plus resource (case) and scoped fields (title and/or data payload). It explicitly separates itself from siblings: 'Other attributes (status, priority, labels) have their own dedicated endpoints,' ruling out bulkUpdateCaseStatus/bulkUpdateCasePriority/assignCaseLabels. An agent can route 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions ('Provide at least one field'), mutual-exclusion rules (data OR json_data, never both), and the case states it applies to (pending, in-progress, settled). It also names the excluded attribute categories and where they live, which is exactly the when-not guidance needed.

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

All Duvo MCP toolsInspect
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