Skip to main content
Glama

get_deployment_schedule

Retrieve schedule details for a Prefect deployment by providing its UUID to manage workflow automation timing and execution patterns.

Instructions

Get a deployment's schedule.

Args: deployment_id: The deployment UUID

Returns: Schedule details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_idYes

Implementation Reference

  • The handler function for the 'get_deployment_schedule' tool. It is decorated with @mcp.tool, which registers it as an MCP tool. The function retrieves the schedule of a Prefect deployment using the Prefect client and returns it as text content.
    @mcp.tool
    async def get_deployment_schedule(
        deployment_id: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Get a deployment's schedule.
        
        Args:
            deployment_id: The deployment UUID
            
        Returns:
            Schedule details
        """
        async with get_client() as client:
            schedule = await client.read_deployment_schedule(UUID(deployment_id))
            
            return [types.TextContent(type="text", text=str(schedule.model_dump()))]
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does ('Get a deployment's schedule') and mentions returns 'Schedule details', but doesn't describe permissions needed, error conditions, rate limits, or what happens if the deployment doesn't exist. For a read operation with zero annotation coverage, this is insufficient.

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 concise with three sentences that each serve a purpose: stating the tool's function, documenting the parameter, and mentioning the return. It's front-loaded with the core purpose. The 'Args' and 'Returns' sections provide clear structure, though the return description could be more specific.

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 no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It covers the basic purpose and parameter but lacks crucial context about authentication requirements, error handling, return format details, and how it differs from sibling tools. For a tool in this environment, more completeness is needed.

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%, so the description must compensate. It documents the single parameter 'deployment_id' and specifies it's a 'UUID', which adds meaningful context beyond the schema's basic 'string' type. However, it doesn't explain where to find this UUID or provide format examples, leaving some 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 with a specific verb ('Get') and resource ('a deployment's schedule'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_deployment' or 'set_deployment_schedule', which would be needed for 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. With siblings like 'get_deployment', 'get_deployments', and 'set_deployment_schedule', there's no indication of when this specific schedule retrieval is appropriate versus getting general deployment information or modifying schedules.

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