Skip to main content
Glama

hz_get_run_summary

Retrieve summary content for a specific run in the Horizon content aggregation and analysis pipeline. Use this tool to access processed data summaries by providing a run identifier.

Instructions

读取指定 run 的摘要内容。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYes
languageNozh

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool hz_get_run_summary is registered using the @mcp.tool() decorator and implemented in server.py, calling the service.get_run_summary helper method.
    @mcp.tool()
    def hz_get_run_summary(run_id: str, language: str = "zh") -> dict[str, Any]:
        """读取指定 run 的摘要内容。"""
    
        started = perf_counter()
        try:
            data = service.get_run_summary(run_id=run_id, language=language)
            elapsed_ms = (perf_counter() - started) * 1000
            _record_metrics("hz_get_run_summary", ok=True, duration_ms=elapsed_ms)
            return _ok("hz_get_run_summary", data, duration_ms=elapsed_ms)
        except Exception as exc:
            elapsed_ms = (perf_counter() - started) * 1000
            payload = _err("hz_get_run_summary", exc, duration_ms=elapsed_ms)
            _record_metrics(
                "hz_get_run_summary",
                ok=False,
                duration_ms=elapsed_ms,
                error_code=payload["error"]["code"],
            )
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('读取' - reads) without any information about permissions, rate limits, response format, or whether this is a safe read operation. This is inadequate for a tool with no annotation coverage.

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 appropriately sized for a simple tool, though it could be more front-loaded with critical information given the lack of annotations.

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 that an output schema exists, the description doesn't need to explain return values. However, for a tool with 2 parameters, 0% schema coverage, and no annotations, the description should provide more context about what 'summary content' means and how it differs from other run-related tools. It's minimally adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions '指定 run' (specified run) which hints at the run_id parameter, but doesn't explain what a run is, what format the ID should be, or mention the language parameter at all. This adds minimal value beyond the bare schema.

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 the tool reads summary content for a specified run, which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like hz_get_run_meta or hz_get_run_stage that also retrieve run-related information, making the purpose somewhat vague in context.

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. With sibling tools like hz_get_run_meta and hz_get_run_stage, there's no indication of what distinguishes this tool's 'summary content' from other run data, leaving usage unclear.

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