Skip to main content
Glama
fortunto2

Prefect MCP Server

by fortunto2

list_flows

Retrieve and manage workflow automation flows from Prefect API to monitor and organize data pipelines.

Instructions

Get a list of flows from the Prefect API.

Args:
    limit: Maximum number of flows to return (default 20).
    offset: Number of flows to skip (default 0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the "list_flows" tool. It is decorated with @mcp.tool() for registration and implements the logic to fetch a paginated list of flows from the Prefect API using the get_client() and returns their model_dump() representations along with the count.
    @mcp.tool()
    async def list_flows(ctx: Context, limit: int = 20, offset: int = 0) -> Dict[str, Any]:
        """Get a list of flows from the Prefect API.
    
        Args:
            limit: Maximum number of flows to return (default 20).
            offset: Number of flows to skip (default 0).
        """
        async with get_client() as client:
            flows = await client.read_flows(limit=limit, offset=offset)
            return {"flows": [flow.model_dump() for flow in flows], "count": len(flows)}
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 this is a read operation ('Get a list'), which implies it's non-destructive, but doesn't mention authentication needs, rate limits, pagination behavior, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 parameter explanations. Every sentence adds value: the first establishes the tool's function, and the subsequent lines clarify parameter semantics. There's no redundant or verbose language.

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 low complexity (2 simple parameters) and the presence of an output schema (which handles return values), the description covers the basics adequately. However, with no annotations and incomplete behavioral context (e.g., missing auth or rate limit info), it doesn't fully prepare an agent for real-world usage, resulting in a minimum viable score.

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?

The description explicitly documents both parameters ('limit' and 'offset') with their purposes and default values, adding meaningful context beyond the schema's basic type information. Since schema description coverage is 0%, this compensates well, but it doesn't explain parameter constraints (e.g., min/max values) or interactions, keeping it at an adequate baseline.

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 ('Get a list of flows') and resource ('from the Prefect API'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'filter_flows' or 'search_flows', which appear to serve similar purposes, so it doesn't reach the highest 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 like 'filter_flows' or 'search_flows'. It mentions the API context but offers no explicit when/when-not instructions or prerequisites for usage, leaving the agent to infer based on tool names alone.

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/fortunto2/prefect-mcp-server'

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