Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

list_machine_manuals

View a list of all machine manuals (PDFs and text files) with file names, sizes, and modification dates to identify available documentation before extracting specifications.

Instructions

    List all available machine manuals in resources/machine_manuals/.

    Returns list of PDFs and text files with filename, size, and modification date.
    Use this to see what manuals are available before extracting specs.

    **IMPORTANT - LLM Usage Guidelines:**
    - This tool returns ONLY the list of available files
    - DO NOT make assumptions about manual content without reading it
    - DO NOT infer specifications without using extract_manual_specs() or read_manual_excerpt()
    - ALWAYS use the returned filenames exactly as-is when calling other tools
    - If user asks about manual content, use read_manual_excerpt() or extract_manual_specs()

    Returns:
        List of dictionaries with manual information

    Example:
        >>> manuals = list_machine_manuals()
        >>> print(f"Found {len(manuals)} manuals")
        >>> for m in manuals:
        ...     print(f"- {m['filename']}: {m['size_mb']:.2f} MB")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that it returns a list of PDFs and text files with filename, size, and modification date, and that it returns a list of dictionaries. While no annotations are provided, the description adequately covers the behavior of a read-only listing operation. A statement about no side effects would be beneficial.

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 main description, usage guidelines, return description, and example. It is slightly verbose but every sentence adds value. Front-loading the main purpose is effective.

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 zero parameters and an output schema, the description is complete. It provides an example, clarifies the return format, and integrates well with the sibling context by guiding subsequent actions.

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 tool has zero parameters and schema coverage is 100%, so the description does not need to explain parameters. The description adds value by clarifying the scope of the listing.

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 specifies listing all machine manuals in a specific directory, with a clear verb and resource. It distinguishes itself from sibling tools like read_manual_excerpt and extract_manual_specs through explicit usage guidelines.

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

Usage Guidelines5/5

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

The description includes a dedicated section 'IMPORTANT - LLM Usage Guidelines' that explicitly states when to use this tool (to see available manuals) and what not to do (infer content without reading). It instructs to use exact filenames and provides guidance on which sibling tools to use for further content extraction.

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