Skip to main content
Glama

get_flow_run

Retrieve detailed information about a specific workflow execution using its unique identifier to monitor status, track progress, and analyze performance.

Instructions

Get details of a specific flow run by ID.

Args: flow_run_id: The flow run UUID

Returns: Flow run details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flow_run_idYes

Implementation Reference

  • The main handler function for the 'get_flow_run' MCP tool. It fetches the flow run details using Prefect client, adds a UI URL, and returns as TextContent.
    @mcp.tool
    async def get_flow_run(
        flow_run_id: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Get details of a specific flow run by ID.
        
        Args:
            flow_run_id: The flow run UUID
            
        Returns:
            Flow run details
        """
        async with get_client() as client:
            flow_run = await client.read_flow_run(UUID(flow_run_id))
            
            # Add UI link
            flow_run_dict = flow_run.dict()
            flow_run_dict["ui_url"] = get_flow_run_url(flow_run_id)
            
            return [types.TextContent(type="text", text=str(flow_run_dict))]
  • Helper function to generate the UI URL for a flow run, used in the get_flow_run handler.
    def get_flow_run_url(flow_run_id: str) -> str:
        base_url = PREFECT_API_URL.replace("/api", "")
        return f"{base_url}/flow-runs/{flow_run_id}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get details'), implying it's non-destructive, but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'details' include. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured 'Args' and 'Returns' sections. Every sentence adds value without redundancy, though the structure could be slightly more polished (e.g., using markdown or consistent formatting).

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 (1 parameter, no output schema, no annotations), the description is minimally complete. It covers the purpose and parameter semantics adequately, but lacks behavioral details and usage guidelines. For a simple read tool, this is acceptable but leaves room for improvement in guiding the agent effectively.

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 adds meaningful context for the single parameter: 'flow_run_id: The flow run UUID.' With 0% schema description coverage, this compensates by specifying the parameter is a UUID, which is crucial information not in the schema. Since there's only one parameter, this effectively covers it, earning a high score despite the low schema coverage.

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: 'Get details of a specific flow run by ID.' It specifies the verb ('Get details') and resource ('flow run'), distinguishing it from siblings like 'get_flow_runs' (plural) and 'get_task_run'. However, it doesn't explicitly differentiate from similar siblings like 'get_task_run' beyond the resource name.

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 siblings like 'get_flow_runs' for listing multiple runs or 'get_task_run' for related resources, nor does it specify prerequisites or exclusions. The usage context is implied but not articulated.

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