Skip to main content
Glama

resume_work_queue

Resume a paused work queue in Prefect to restart workflow execution. Provide the work queue UUID to activate queued tasks and resume automated processes.

Instructions

Resume a work queue.

Args: work_queue_id: The work queue UUID

Returns: Details of the updated work queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
work_queue_idYes

Implementation Reference

  • The implementation of the 'resume_work_queue' tool. This async function is decorated with @mcp.tool, which registers it as an MCP tool. It takes a work_queue_id, unpauses the queue via Prefect client (sets is_paused=False), reads the updated queue, and returns its details as text content.
    @mcp.tool
    async def resume_work_queue(
        work_queue_id: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Resume a work queue.
        
        Args:
            work_queue_id: The work queue UUID
            
        Returns:
            Details of the updated work queue
        """
        async with get_client() as client:
            await client.update_work_queue(
                id=UUID(work_queue_id),
                is_paused=False
            )
            
            # Read the updated work queue to return its details
            updated_work_queue = await client.read_work_queue(UUID(work_queue_id))
            return [types.TextContent(type="text", text=str(updated_work_queue.model_dump()))]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that it returns 'details of the updated work queue' but doesn't specify what 'resume' means operationally (e.g., whether it restarts processing, requires permissions, or has side effects). This leaves significant gaps for a mutation tool.

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?

The description is appropriately sized with a clear main sentence and structured Args/Returns sections. It's front-loaded with the core purpose, though the Args/Returns formatting is slightly verbose for a single parameter.

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

Completeness3/5

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

Given no annotations, no output schema, and a mutation tool with 1 parameter, the description is minimally adequate. It covers the basic action and parameter semantics but lacks details on behavior, usage context, or return values, leaving room for improvement.

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?

The description adds meaning by specifying that 'work_queue_id' is a 'UUID', which clarifies the format beyond the schema's generic 'string' type. With 0% schema description coverage and only 1 parameter, this compensates adequately, though it could note that this is a required identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'resume' and the resource 'work queue', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'pause_work_queue' or explain what 'resuming' entails in this context, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'pause_work_queue' or 'update_work_queue', nor does it mention prerequisites (e.g., the work queue must be paused). The description only states what it does without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/allen-munsch/mcp-prefect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server