Skip to main content
Glama
Svel26

Sigmatek LASAL MCP Server

by Svel26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hmi_runtime

Manage the HMI runtime DataService by starting, stopping, or checking its status. Optionally publish the project and spawn the DataService for web interaction.

Instructions

Start, stop, or check the local HMI web simulation (LasalVISUDataService). Publishes the project, copies webroot, and spawns the DataService. Use hmi_browser to interact with it afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform on the HMI runtime DataService.
lvp_pathNoAbsolute path to the .lvp file. Omit to use the currently selected project.
debugPublishNoUse debug publish (requires TypeScript project support). Fallback to standard publish on failure. Default true.
publishFirstNoPublish the project before starting the DataService. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

No annotations, so description must disclose side effects. It explicitly mentions publishing, copying webroot, and spawning the DataService, which are relevant side effects. Does not mention potential cleanup on stop, but acceptable.

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?

Two sentences, no redundant information, well-structured.

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?

Complete for the tool's purpose; no output schema, so no need to explain returns. Mentions service name and interaction pointer.

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

Parameters3/5

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

Schema covers all parameters with descriptions; description adds no additional semantics beyond restating publishFirst. Baseline 3.

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?

States a specific verb (start/stop/check), the resource (local HMI web simulation, LasalVISUDataService), and differentiates from hmi_browser by pointing to it for interaction. Clear and specific.

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?

Provides a hint to use hmi_browser for interaction after starting, but does not explicitly compare with lars_runtime or other management tools. Implicit usage context is clear, but explicit differentiation is lacking.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools