Skip to main content
Glama
GJakobi

Hatchet MCP Server

by GJakobi

list_workflows

Retrieve all registered workflows from the Hatchet MCP Server to monitor and debug workflow execution, including IDs, names, and descriptions.

Instructions

List all registered Hatchet workflows.

Returns a list of workflows with their IDs, names, and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `list_workflows` tool is implemented as an async function decorated with `@mcp.tool()`. It uses the Hatchet client to fetch workflows and serializes them using `_serialize_workflow`.
    @mcp.tool()
    async def list_workflows() -> list[dict]:
        """
        List all registered Hatchet workflows.
    
        Returns a list of workflows with their IDs, names, and descriptions.
        """
        try:
            hatchet = get_hatchet_client()
            workflows = await hatchet.workflows.aio_list()
            return [_serialize_workflow(w) for w in (workflows.rows or [])]
        except Exception as e:
            return [{"error": str(e)}]
Behavior3/5

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It partially satisfies this by specifying return fields (IDs, names, descriptions), but omits critical safety characteristics (read-only nature, idempotency), pagination behavior, or performance implications of listing 'all' workflows.

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?

Extremely efficient two-sentence structure: first sentence declares purpose, second declares return payload. Every word earns its place with no redundancy or extraneous text.

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

Completeness4/5

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

Appropriate for a zero-parameter list operation with existing output schema. Previewing the return fields (IDs, names, descriptions) provides helpful context without duplicating the full schema. Minor gap: lacks mention of pagination behavior or maximum result limits typical for unfiltered 'list all' endpoints.

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?

Input schema contains zero parameters, establishing a baseline score of 4 per evaluation rules. The description appropriately does not invent parameter documentation where none exist.

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?

Uses specific verb 'List' with clear resource 'registered Hatchet workflows'. Effectively distinguishes from siblings like 'list_runs' and 'search_runs' through explicit use of 'workflows' terminology, though could be strengthened by explicitly contrasting workflow definitions versus run executions.

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?

Contains no guidance on when to select this tool over alternatives. Does not clarify the distinction between retrieving workflow definitions (this tool) versus querying run executions (list_runs/search_runs siblings), leaving the agent to infer from naming 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/GJakobi/hatchet-mcp'

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