Skip to main content
Glama

hz_list_runs

List recent pipeline runs and their stage statuses to monitor Horizon content aggregation and analysis progress.

Instructions

列出最近运行记录与阶段状态。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation and registration of the hz_list_runs tool handler.
    @mcp.tool()
    def hz_list_runs(limit: int = 20) -> dict[str, Any]:
        """列出最近运行记录与阶段状态。"""
    
        started = perf_counter()
        try:
            data = service.list_runs(limit=limit)
            elapsed_ms = (perf_counter() - started) * 1000
            _record_metrics("hz_list_runs", ok=True, duration_ms=elapsed_ms)
            return _ok("hz_list_runs", data, duration_ms=elapsed_ms)
        except Exception as exc:
            elapsed_ms = (perf_counter() - started) * 1000
            payload = _err("hz_list_runs", exc, duration_ms=elapsed_ms)
            _record_metrics(
                "hz_list_runs",
                ok=False,
                duration_ms=elapsed_ms,
                error_code=payload["error"]["code"],
            )
            return payload
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions listing 'recent' runs and stage status, implying a read-only operation, but doesn't disclose behavioral traits like pagination, ordering, rate limits, authentication needs, or what 'recent' means (e.g., time-based or count-based). For a list operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 a single, efficient sentence in Chinese that directly states the tool's function. It's front-loaded with the core purpose and avoids unnecessary words. However, it could be slightly more specific (e.g., clarifying 'recent'), but overall it's appropriately concise.

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 has an output schema (which should document return values), no annotations, and a simple input schema with one optional parameter, the description is minimally adequate. It states what the tool does but lacks context on usage relative to siblings and behavioral details. For a list tool with output schema support, this is the bare minimum to be functional.

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 input schema has one parameter (limit) with 0% description coverage, so the schema provides no semantic context. The description doesn't mention parameters at all, but since there's only one optional parameter with a default value, the baseline is high. The tool likely functions without any input, and the limit parameter is straightforward, so the lack of parameter explanation is less critical.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states '列出最近运行记录与阶段状态' (List recent run records and stage status), which provides a basic verb+resource combination. However, it's vague about scope ('recent' is ambiguous) and doesn't differentiate from sibling tools like hz_get_run_meta, hz_get_run_stage, or hz_get_run_summary that also appear to retrieve run-related information. The purpose is understandable but lacks specificity.

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 is provided on when to use this tool versus alternatives. With multiple sibling tools related to runs (hz_get_run_meta, hz_get_run_stage, hz_get_run_summary, hz_run_pipeline), the description offers no context about distinctions, prerequisites, or exclusions. The agent must infer usage from the tool name 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/henry-insomniac/Horizon-mcp'

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