Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

get_signal_info

Retrieve metadata for a stored signal without loading the full array. Includes source metadata, sampling rate, unit, shape, and timestamps.

Instructions

Get metadata for a stored signal without loading the full array.

Includes the COMPLETE companion-metadata dict (source_metadata: rpm/
shaft_speed, reference frequencies, ...) alongside the repository
fields (sampling_rate, declared signal_unit, shape, timestamps).

Args:
    ctx: MCP context.
    signal_id: ID of a signal previously loaded via load_signal.

Returns:
    StoredSignalInfo with source_metadata populated from the companion
    _metadata.json (empty dict when the file has none).

Raises:
    ValueError: If the signal_id is not in the repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
shapeYesShape of the signal array
filepathYesOriginal file path
signal_idYesUnique identifier for the stored signal
duration_sNoDuration in seconds
size_bytesYesApproximate memory size in bytes
num_samplesYesNumber of samples
signal_unitNoDECLARED signal unit — from load_signal(signal_unit=...) or the companion _metadata.json ('signal_unit' field). Never guessed. None means undeclared: ISO severity verdicts will be refused until the unit is declared.
sampling_rateNoSampling rate in Hz (must be positive when set)
load_timestampYesISO 8601 timestamp when signal was loaded
source_metadataNoComplete companion _metadata.json of the source file (rpm/shaft_speed, reference frequencies, ...). Empty when the file has no companion metadata.
Behavior4/5

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

No annotations exist, so the description carries full weight. It discloses that the tool returns metadata (including companion-metadata dict) and does not load the full array, and raises ValueError for invalid IDs. This is sufficient behavioral transparency for a read-only metadata retrieval tool.

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 well-structured with a concise main sentence followed by clearly labeled Args, Returns, and Raises sections. Every sentence is informative without redundancy, making it highly efficient for an AI agent.

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?

The tool has an output schema and a single parameter. The description fully covers purpose, parameter usage, return structure, and error conditions. Given the simplicity and the presence of an output schema, the description is complete and self-contained.

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?

Schema description coverage is 0%, so the description must compensate. It explains the parameter signal_id as 'ID of a signal previously loaded via load_signal,' adding essential context beyond the schema's name. The returns and raises also add semantic value.

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 'Get metadata for a stored signal without loading the full array,' specifying the verb (Get), resource (metadata for a stored signal), and a distinguishing behavior (not loading full array). It further details included fields, making the purpose explicit and distinct from siblings like load_signal.

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 provides usage context: signal_id must be from a previously loaded signal (via load_signal). It lists returns and raises, implying when to use. However, it lacks explicit when-not-to-use or alternative tool comparisons, though the context is clear enough.

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