Skip to main content
Glama

create_work_queue

Create a work queue to organize and manage workflow execution in Prefect, allowing control over queue behavior with options for pausing, concurrency limits, and descriptions.

Instructions

Create a work queue.

Args: name: The name for the work queue description: Optional description is_paused: Whether the queue should be paused upon creation concurrency_limit: Optional concurrency limit

Returns: Details of the created work queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
concurrency_limitNo
descriptionNo
is_pausedNo
nameYes

Implementation Reference

  • The handler function for the 'create_work_queue' tool, decorated with @mcp.tool for registration. It uses the Prefect client to create a work queue with the provided parameters and returns the created work queue details as text content.
    @mcp.tool
    async def create_work_queue(
        name: str,
        description: Optional[str] = None,
        is_paused: Optional[bool] = None,
        concurrency_limit: Optional[int] = None,
        work_pool_name: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Create a work queue.
        
        Args:
            name: The name for the work queue
            description: Optional description
            is_paused: Whether the queue should be paused upon creation
            concurrency_limit: Optional concurrency limit
            work_pool_name: Optional work pool name to create the queue in
            
        Returns:
            Details of the created work queue
        """
        async with get_client() as client:
            work_queue = await client.create_work_queue(
                name=name,
                description=description,
                is_paused=is_paused,
                concurrency_limit=concurrency_limit,
                work_pool_name=work_pool_name,
            )
            
            return [types.TextContent(type="text", text=str(work_queue.model_dump()))]
  • The import statement in main.py that loads the work_queue module, thereby registering all tools defined in it (including create_work_queue) via their @mcp.tool decorators.
    if APIType.WORK_QUEUE.value in apis:
        info("Loading Work Queue API...")
        from . import work_queue
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 states the action ('Create') but doesn't cover critical aspects like required permissions, whether the creation is idempotent, rate limits, or what happens on failure. The return statement is vague ('Details of the created work queue'), offering minimal insight into output behavior.

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 well-structured with clear sections for Args and Returns, making it easy to parse. It's front-loaded with the core purpose. However, the return statement is somewhat vague, and the overall text could be more concise by integrating parameter details more tightly, but it remains efficient with minimal fluff.

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 complexity (a creation tool with 4 parameters), no annotations, and no output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks behavioral details, error handling, and explicit output structure. It's adequate as a minimum viable description but has clear gaps for effective tool invocation.

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 description coverage is 0%, so the description must compensate. It lists all four parameters with brief explanations (e.g., 'name: The name for the work queue'), adding meaningful context beyond the schema's property names. However, it doesn't detail constraints like name uniqueness or concurrency limit ranges, leaving some semantic gaps.

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 tool's purpose: 'Create a work queue.' It specifies the verb ('Create') and resource ('work queue'), making it unambiguous. However, it doesn't differentiate from sibling tools like 'update_work_queue' or 'get_work_queue' beyond the obvious action difference, which keeps it from 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a workspace or permissions, or when to choose 'create_work_queue' over 'update_work_queue' or 'get_work_queue'. This lack of context leaves the agent without usage direction.

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