Skip to main content
Glama
Red5d

Beszel MCP Server

by Red5d

list_alert_history

Retrieve historical records of triggered alerts from the Beszel monitoring system. Use filters, pagination, and sorting to analyze past alert data for infrastructure monitoring.

Instructions

List alert history in Beszel.

Args: page: Page number (default: 1) per_page: Number of results per page (default: 50) filter: PocketBase filter string sort: Sort order (e.g., "-created" for most recent first)

Returns: Dictionary containing historical records of triggered alerts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo
filterNo
sortNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_alert_history' tool. It is registered via the @mcp.tool() decorator and implements the logic to retrieve paginated alert history records from the 'alerts_history' PocketBase collection using shared client utilities.
    @mcp.tool()
    async def list_alert_history(
        page: int = 1,
        per_page: int = 50,
        filter: Optional[str] = None,
        sort: Optional[str] = None,
    ) -> dict:
        """List alert history in Beszel.
        
        Args:
            page: Page number (default: 1)
            per_page: Number of results per page (default: 50)
            filter: PocketBase filter string
            sort: Sort order (e.g., "-created" for most recent first)
        
        Returns:
            Dictionary containing historical records of triggered alerts
        """
        client = get_client()
        await ensure_authenticated(client)
        
        return await client.get_list(
            collection="alerts_history",
            page=page,
            per_page=per_page,
            filter=filter,
            sort=sort,
        )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions pagination defaults and filtering/sorting capabilities, it doesn't address important behavioral aspects like rate limits, authentication requirements, error conditions, or what constitutes 'historical records of triggered alerts' versus current alerts.

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?

The description is efficiently structured with a clear purpose statement followed by well-organized Args and Returns sections. Every sentence adds value - the purpose statement is direct, parameter explanations are concise yet informative, and the return statement is appropriately brief given the existence of an output schema.

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?

For a read-only listing tool with 4 parameters and an output schema, the description provides good coverage. The parameter documentation is excellent, and the existence of an output schema means the return value description is sufficient. The main gap is lack of differentiation from sibling tools and some behavioral context that would be helpful for a tool with filtering capabilities.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing clear documentation for all 4 parameters. Each parameter gets a helpful explanation including defaults, examples ('-created' for sort), and the nature of 'PocketBase filter string' - adding significant value beyond the bare schema.

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 verb 'List' and resource 'alert history in Beszel', making the purpose explicit. However, it doesn't distinguish this tool from sibling tools like 'list_alerts' - the difference between 'alert history' and 'alerts' isn't explained, preventing a perfect score.

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 about when to use this tool versus alternatives like 'list_alerts' or other sibling tools. The description mentions filtering and sorting capabilities but doesn't explain when these features would be appropriate or when other tools might be better suited.

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/Red5d/beszel-mcp'

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