Skip to main content
Glama
GJakobi

Hatchet MCP Server

by GJakobi

get_run_status

Check the current status and details of a specific workflow run by providing its run ID to monitor execution progress.

Instructions

Get the current status of a specific workflow run.

Args: run_id: The ID of the workflow run

Returns the run's current status and details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYes

Implementation Reference

  • The get_run_status tool handler, registered with @mcp.tool(), fetches and serializes the status of a Hatchet workflow run.
    @mcp.tool()
    async def get_run_status(run_id: str) -> dict:
        """
        Get the current status of a specific workflow run.
    
        Args:
            run_id: The ID of the workflow run
    
        Returns the run's current status and details.
        """
        try:
            hatchet = get_hatchet_client()
            status = await hatchet.runs.aio_get(run_id)
            return _serialize_run(status)
        except Exception as e:
            return {"error": str(e), "run_id": run_id}
Behavior3/5

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

No annotations provided, so description carries full burden. States it returns 'current status and details' implying a read operation, but doesn't specify possible status values (running/completed/failed), whether data is real-time or cached, or what 'details' includes.

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?

Front-loaded with clear purpose sentence. 'Args' and 'Returns' sections are structured and functional given lack of schema/output descriptions. No redundant or wasted sentences, though docstring-style formatting is slightly verbose.

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?

Adequate for a single-parameter read operation. Mentions return value (status/details) to compensate for missing output schema, and describes the parameter to compensate for 0% schema coverage. However, sibling tool confusion (result vs status) leaves a gap that should be addressed.

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 has 0% description coverage (only 'title': 'Run Id'). Description adds 'The ID of the workflow run' which provides basic context, but with only one parameter and no schema docs, it could elaborate on ID format or source (e.g., obtained from list_runs).

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?

Clear verb+resource ('Get the current status of a specific workflow run'), but lacks differentiation from sibling 'get_run_result' (status vs. output data) and 'list_runs' (specific vs. list).

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 on when to use this versus 'get_run_result' (which also takes a run_id) or when to prefer 'list_runs' followed by this call. No prerequisites mentioned (e.g., obtaining run_id from list_runs).

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/GJakobi/hatchet-mcp'

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