Skip to main content
Glama

pause_work_queue

Stop a Prefect work queue from processing new workflow runs by providing its UUID, temporarily halting automated task execution.

Instructions

Pause 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 'pause_work_queue' tool handler. This async function is decorated with @mcp.tool, which registers it as an MCP tool. It uses the Prefect client to update the specified work queue by setting is_paused=True and returns the details of the updated work queue.
    @mcp.tool
    async def pause_work_queue(
        work_queue_id: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Pause 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=True
            )
            
            # 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,' which hints at a mutation with a response, but doesn't specify whether this requires special permissions, if it's reversible, what 'pause' entails operationally, or any rate limits. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value without redundancy, making it easy to parse and understand quickly.

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 the tool's complexity (a mutation with no annotations and no output schema), the description is minimally adequate. It covers the basic purpose and parameter, but lacks details on behavioral traits, usage context, and output specifics, leaving room for improvement in completeness.

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 explicitly documents the single parameter 'work_queue_id' as 'The work queue UUID,' adding semantic meaning beyond the schema's 0% coverage. Since there's only one parameter and it's fully explained in the description, this compensates well for the lack of schema descriptions.

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 ('Pause') and resource ('a work queue'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'resume_work_queue' or 'delete_work_queue' beyond the obvious action difference, 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 'resume_work_queue' or 'delete_work_queue', nor does it mention prerequisites or context. The description only states what it does, not when or why to use it.

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