Duvo MCP

Resume Queue

resumeQueue

Resume a paused queue. Its pending cases start on the next dispatch, within the queue's concurrency limit. Resuming a queue that is not paused changes nothing. Only a builder or team admin, or someone whose case trigger on the queue is on, can resume it.

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>"
    },
    "name": "resumeQueue"
  }
}

Input Schema

Name	Required	Description	Default
`queue_id`	Yes	The queue's unique identifier

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare this as a non-read-only, non-destructive mutation, but the description adds material behavior beyond them: pending cases start on the next dispatch, bounded by the queue concurrency limit, and non-paused resumes are no-ops. It also discloses the permission model, which is important for deciding whether the call is allowed.

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 short sentences, front-loaded with the action and effect, then the no-op caveat, then the permission requirement. No filler; each sentence carries needed information.

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?

For a one-parameter mutation with no output schema, the description supplies the effect, dispatch timing, no-op behavior, and authorization requirements. Nothing essential for correct invocation is missing.

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?

The schema has 100% description coverage and only one required parameter, queue_id, which is fully documented in the schema. The description adds no parameter-specific syntax or format beyond general queue context, so the 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?

The description opens with a specific verb and resource ('Resume a paused queue') and immediately scopes the effect to pending cases, so an agent can distinguish it from pauseQueue, createQueue, and updateQueue.

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 states the triggering condition (a paused queue) and the no-op case (resuming a non-paused queue). It does not explicitly name pauseQueue or another alternative, so it falls short of full when-to-use/when-not/alternative guidance.

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?