Skip to main content
Glama

delete_work_queue

Remove a work queue from Prefect's workflow automation platform by specifying its unique identifier to manage workflow resources effectively.

Instructions

Delete a work queue by ID.

Args: work_queue_id: The work queue UUID

Returns: Confirmation message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
work_queue_idYes

Implementation Reference

  • Handler function for the 'delete_work_queue' MCP tool. It deletes the work queue using Prefect client and returns a success message.
    @mcp.tool
    async def delete_work_queue(
        work_queue_id: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Delete a work queue by ID.
        
        Args:
            work_queue_id: The work queue UUID
            
        Returns:
            Confirmation message
        """
        async with get_client() as client:
            # Correct method name is delete_work_queue_by_id
            await client.delete_work_queue_by_id(UUID(work_queue_id))
            
            return [types.TextContent(type="text", text=f"Work queue '{work_queue_id}' deleted successfully.")]
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral details. It mentions deletion but doesn't disclose if this is irreversible, requires specific permissions, affects associated resources, or has rate limits. The confirmation message return is noted, but no further context on behavior is given.

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 and front-loaded with the main purpose in the first sentence. The Args and Returns sections are structured but slightly verbose; every sentence adds value, though it could be more streamlined without losing clarity.

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

Completeness2/5

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

Given the complexity of a deletion tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral implications, error handling, and usage context, making it inadequate for safe and effective tool invocation by an AI agent.

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?

Schema description coverage is 0%, but the description adds meaning by specifying 'work_queue_id' as a UUID, which clarifies the parameter type beyond the schema's 'string' type. However, it doesn't explain format constraints or provide examples, leaving some gaps in understanding.

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 action ('Delete') and resource ('a work queue by ID'), making the purpose specific and understandable. It distinguishes itself from siblings like 'pause_work_queue' or 'resume_work_queue' by indicating permanent removal, though it doesn't explicitly contrast with all alternatives like 'update_work_queue'.

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. It doesn't mention prerequisites (e.g., ensure the queue is empty or paused), exclusions, or compare with sibling tools like 'delete_flow' or 'delete_deployment' for context-specific decisions.

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