Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

list_html_reports

List all HTML reports with metadata or retrieve embedded metadata for a specific report. Avoids returning HTML content to conserve tokens.

Instructions

    List HTML reports, or get one report's embedded metadata.

    Without file_name: lists every report in reports/ with file name,
    type, signal, and size. With file_name: returns that report's
    embedded metadata block (absorbed get_report_info). Never returns
    HTML content — metadata only, to avoid token consumption.

    Args:
        file_name: Optional report filename inside reports/ — returns
            its metadata instead of the listing.

    Returns:
        List of report summaries (no file_name), or a dict with the
        single report's metadata (file_name given).

    Raises:
        ValueError: If file_name escapes the reports directory, does
            not exist, or carries no metadata block.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully carries the burden. It explicitly states it never returns HTML content (to avoid token consumption), describes return types (list vs dict), and details error conditions (ValueError for invalid file_name). This provides rich behavioral context.

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 well-structured with a summary line followed by details. It is relatively lengthy but every sentence adds value. It is front-loaded with the main purpose. Slightly verbose but efficient overall.

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

Completeness5/5

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

Given the simple tool with one optional parameter and an existing output schema, the description covers all user needs: the dual mode behavior, return types, error cases, and even mentions that it absorbed get_report_info. No gaps remain.

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?

Schema description coverage is 0%, so the description compensates fully. It explains that file_name is optional, and when provided, returns metadata instead of the listing. It also specifies valid scope (inside reports/) and the effect on the output, adding significant meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the tool lists HTML reports or retrieves a single report's embedded metadata, with explicit distinction between the two modes. It differentiates from sibling tools by emphasizing it never returns HTML content, only metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use each mode (with or without file_name) and the behavior for each. However, it does not provide explicit guidance on when not to use this tool versus alternatives like get_signal_info, leaving a slight gap in usage exclusions.

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/LGDiMaggio/predictive-maintenance-mcp'

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